Refactoring the notification Section #2047
Closed
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
check if this message is sent to the user before
Switch to use "sonner" to handle notification logic efficiently
Use gradient instead of images to improve loading time
Move all the logic to "NotificationToast.tsx" to keep "App.tsx" clean and minimal
|
@OM3X4 is attempting to deploy a commit to the Arc53 Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Refactoring the notification Section to:
check if this message is sent to the user before
Switch to use "sonner" to handle notification logic efficiently
Use gradient instead of images to improve loading time
Move all the logic to "NotificationToast.tsx" to keep "App.tsx" clean and minimal
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) : Refactoring
Why was this change needed? (You can also link to an open issue here): issue Refactoring The Notification Section #2046
Other information: