Skip to content

[NTP Next] Split app context by functionality #45794

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.

Sign up for GitHub

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

Jump to bottom
Open
zenparsing opened this issue May 1, 2025 · 0 comments · May be fixed by brave/brave-core#28910
Open

[NTP Next] Split app context by functionality #45794

zenparsing opened this issue May 1, 2025 · 0 comments · May be fixed by brave/brave-core#28910
Assignees
@zenparsing
Labels
dev-concern feature/new-tab OS/Desktop priority/P3 The next thing for us to work on. It'll ride the trains. QA/No release-notes/exclude

Comments

@zenparsing
Copy link

Currently, all UI "models" are provided to components via a single context (AppContext), which joins together the state and actions from each model. In order to provide more flexibility, we would like to have separate contexts for each UI model (e.g. search/rewards/etc.)
@zenparsing zenparsing self-assigned this May 1, 2025
@zenparsing zenparsing linked a pull request May 1, 2025 that will close this issue
Open
@rebron rebron added the priority/P3 The next thing for us to work on. It'll ride the trains. label May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zenparsing zenparsing

Labels
dev-concern feature/new-tab OS/Desktop priority/P3 The next thing for us to work on. It'll ride the trains. QA/No release-notes/exclude
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[NTP Next] Separate model context providers brave/brave-core
2 participants
@rebron @zenparsing