-
Notifications
You must be signed in to change notification settings - Fork 1k
Remove reference to LitElement in lit-labs/motion #2239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: d21bc4b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@justinfagnani Thoughts? |
|
cc @sorvell |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
I'm mostly ok with this. My one concern is that we don't find a need for having a LitElement host in the future. (edit: oops, this requires a ReactiveControllerHost) |
|
Any updates for this? |
📊 Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultsthis-change
render
update
update-reflect
this-change, tip-of-tree, previous-release
render
update
nop-update
this-change, tip-of-tree, previous-release
render
update
this-change, tip-of-tree, previous-release
render
update
update-reflect
|
augustjk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for taking so long to get to this. The changes here make sense.
I rebased to current main, resolving conflict, and added a changeset.
Thank you very much for the contribution!
|
The size of lit-html.js and lit-core.min.js are as expected. |
The animate controller should be compatible with any component implementing
ReactiveControllerHostnot only LitElement, see #2197