Walkthrough updates for development easy-of-use and RN 0.68 #43
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
* Update some dependencies (these seemed to be required to support RN 0.68) * Add `debug` option to make development easier * Allow listening to possible outcomes while to tooltip is displayed * Add warning for duplicate element IDs
apfritts
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi @jasongaare!
Another quick update that we're using in our app. We recently updated to RN 0.68 and some typing seemed to be off so I updated some dependencies and, as I was developing, found a few sharp edges that I hope this can help prevent other developers from running into.
There is one new feature: listening for possible outcomes while the tooltip is displayed rather than only after it is displayed. I realize now as I write this, it probably would have been better to separate that into a totally separate flag rather than reusing
possibleOutcomes. Let me know your thoughts on that.debugoption to make development easierPlease let me know if there is anything you don't think belongs in here!