-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose notifications API as non-hook functions #62
Labels
enhancement
New feature or request
Comments
9 tasks
lmatejic-CROZ
added a commit
that referenced
this issue
Apr 19, 2024
9 tasks
lmatejic-CROZ
added a commit
that referenced
this issue
Apr 19, 2024
jtomic-croz
pushed a commit
that referenced
this issue
Apr 19, 2024
jtomic-croz
added a commit
that referenced
this issue
Apr 19, 2024
#62 Added missing export statement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basic information
Enhancement description
Currently the only way to use the notifications API is via the
useNotifications
hook. There are instances where we need just standard JS functions to satisfy the React naming conventions and linters. One such example is using the notifications with API calls or related interceptors which are not a hook or part of a React component.As-is, the current logic would work even outside of React components, so it's basically only required to re-export under a different naming convention.
The text was updated successfully, but these errors were encountered: