Exposed notification API 'add' and 'remove' methods as non-hook function variants. #63
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.
Basic information
Additional information
Resolving #62
Description
Summary
Re-exported methods to satisfy naming conventions of React hooks and enable them to be used as non-hook variants.
Details
Separated the store creation into a variable and exported as the currently used
useNotificationsStore
hook to keep compatibility. Added 2 more exports to enable the methods being available as standard (non-hook) functions.Related issue
#62
Types of changes
Checklist
I have added tests to cover my changes-> the logic is unchanged, changes are semantic by nature