fix(types): fix useRunInJS type not allowing functions to have args
#162
Conversation
This file contains hidden or 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
hannojg
approved these changes
Apr 8, 2024
Member
hannojg
left a comment
hannojg
left a comment
There was a problem hiding this comment.
LGTM, thanks for the contribution!
hannojg
changed the title
useRunInJS type.useRunInJS type not allowing for functions to have arguments
hannojg
changed the title
useRunInJS type not allowing for functions to have argumentsuseRunInJS type not allowing functions to have args
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The current type of
useRunInJSdoesn't allow any argument.[]toany[]allows arguments in arbitrary length.