[User Model] [Fix] Notification permission change event stop firing #1072
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.
Description
1 Line Summary
Fix bug where notification permission change would stop firing due to a bad state.
Details
There was an early return on shouldBeUpdated that caused executing to never become false again. To prevent this issue with future code changes made a new privateTriggerNotificationPermissionChanged to encapsulate the executing state. Also added a try..finally to prevent throwing from creating a bad state.
Validation
Tests
Tested on Chrome on macOS. Toggle notifications on and off and observed bell icon and custom link change, where it was broken before.
Info
Checklist
Programming Checklist
Interfaces:
Functions:
Typescript:
Other:
elem of array
syntax. PreferforEach
or usemap
context
if possible. Instead, we can pass it to function/constructor so that we don't callOneSignal.context
Screenshots
Info
Checklist
Related Tickets
Bug was introduced in PR #1050
This PR mirrors the same fix from main's #1071 PR.
This change is