feature: 141-FEATURE-News-notifications-extension-frontend #148
Conversation
This file contains 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
Fixes #141
…ns-extension-frontend
|
We should target the PR to |
lmcmz
reviewed
Nov 7, 2024
| }} | ||
| /> | ||
| <Main /> | ||
| <NewsProvider> |
There was a problem hiding this comment.
Is there a way to avoid too many providers ?
It's fine for now, but when the pattern built up might be too many providers in here.
Cause the news is a light feature in the app.
Any thoughts? @tombeckenham
There was a problem hiding this comment.
I think if we had better state management it could be avoided.
tombeckenham
deleted the
tombeckenham/141-FEATURE-News-notifications-extension-frontend
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implementation of News notifications on the chrome extension.
Fixes #141