fix: removes Inject plugins #837
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
oscb
pushed a commit
that referenced
this pull request
Jun 2, 2023
## [@segment/analytics-react-native-v2.15.0](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-v2.14.0...@segment/analytics-react-native-v2.15.0) (2023-06-02) ### Features * add config option for cdn proxy ([#834](#834)) ([95562ed](95562ed)) ### Bug Fixes * fix flush policies reference copy, add BackgroundPolicy ([#838](#838)) ([e4b558a](e4b558a)) * queue storage fixes ([#836](#836)) ([f5a6a86](f5a6a86)) * removes Inject plugins ([#837](#837)) ([ce56c9e](ce56c9e)) * update braze example and readme ([#830](#830)) ([b6a319a](b6a319a))
|
🎉 This PR is included in version @segment/analytics-react-native-v2.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Adding and storing context and userInfo is now completely handled in the client, outside of the timeline.
This is to prevent concurrency issues in the timeline where plugins could hold off updating the userInfo, or direct operations like
resetcould cause an processing event to contain information not representative from the sequential order when it was captured.applyRawEventDatanow is the capture moment before timeline/plugin processing starts, capturing all the data relevant to the event at a single moment.This is the first step towards completely removing shared state.
InjectContextandInjectUserInfopluginsInjectTraitsexample too as it is now discouraged to access shared state from any plugin. (Plugins should operate only with event data or its own state).fetchSettingsfirst before triggering any lifecycle and context events. This guarantees plugins that use SegmentSettings will have them available before any events are captured. (WIP)