feat: Allow setting Braze instance and override notification handling #87
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.
Summary
Due to the partner SDK changes (from Appboy to Braze) the implementation changed a bit and the kit was no longer to fully handle attribution to Braze for notifications that open the app (cold start).
These changes allow customers to inform the kit that they will handle notifications in their app code as well as allowing them to set their own braze instance to the kit (which is required to handle notifications manually).
Docs updates will be forthcoming.
Testing Plan
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)