1.1.1 - #86
Merged
Merged
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
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.
Patch release for the public-method binding fix merged in #85.
What changed
@formo/analytics-react-nativefrom1.1.0to1.1.1.src/version.tsconstant to1.1.1.Impact
Consumers can safely destructure public SDK methods from
useFormo(), includingreset(), without losing the SDK instance asthis. This fixes logout-time crashes and protects the other public methods covered by the binding regression suite.Validation
examples/with-react-native; Expo web initialized successfully and a destructuredreset()loggedE2E_RESET_OK.Release after merge
Tag the merge commit as
v1.1.1and push the tag. The Publish Package workflow will build, test, publish to npm with provenance, and create the GitHub release.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.