Skip to content

Move CurrentUserProvider into its own file - #2

Merged
nando-bingani merged 1 commit into
mainfrom
split-current-user-provider
Oct 7, 2026
Merged

nando-bingani merged 1 commit into
mainfrom
split-current-user-provider

Conversation

@nando-bingani

Copy link
Copy Markdown
Collaborator

CurrentUserContext.jsx exported a component (the provider) next to a hook, the one lint warning left in the app (react-refresh/only-export-components): Vite's fast refresh can't hot-reload such a file. The provider now lives in CurrentUserProvider.jsx; the context and useCurrentUser stay where every import and test mock already expects them, so only main.jsx changes.

CurrentUserContext.jsx exported a component (the provider) next to a hook,
the one lint warning left in the app (react-refresh/only-export-components):
Vite's fast refresh can't hot-reload such a file. The provider now lives in
CurrentUserProvider.jsx; the context and useCurrentUser stay where every
import and test mock already expects them, so only main.jsx changes.
@nando-bingani
nando-bingani merged commit 9aaf17a into main Oct 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant