Add dynamic keys on useMotion directives when calling apply() and other methods #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Nice work :) I think we can get rid of these |
This was referenced Jun 20, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@Tahul
Adding support for strict typing of the directive keys when creating a motion instance using useMotion and other methods.
I've also added a few other
// @ts-expect-errorthat seemed to be missing and causedtscto throw errors. I believe it is cleaner to do it this way rather than dokeyof typeof objin every place, since it's something that TypeScript don't intend to change (microsoft/TypeScript#12253 (comment)).