-
Notifications
You must be signed in to change notification settings - Fork 9
VIDSOL-281: refactor app config context for scoped reactivity and stable rests #251
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
base: johnny/vidsol-280-unit-test-fixes-and-refinements
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
a4c1660 to
57d7614
Compare
a0d05c8 to
6d8ac7f
Compare
57d7614 to
b10a7fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 83 out of 84 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
frontend/src/components/HiddenParticipantsTile/HiddenParticipantsTile.spec.tsx
Outdated
Show resolved
Hide resolved
2182b81 to
77170d3
Compare
- using granular context for app configuration... avoid re-renders and isolate logic - adding reusable provider wrappers for unit test - removing a bunch of mocks in our unit test... mocking our own code downgrades the quality of the test
77170d3 to
55e2440
Compare
|



What is this PR doing?
This PR refactors the AppConfigContext to isolate updates and stop global re-renders.
It forces components to subscribe only to the specific configuration keys they depend on, eliminating unnecessary re-renders and improving overall performance.
It also introduces the isAppConfigLoaded flag to stabilize initialization and prevent UI flickers.
Additionally, it removes excessive mocking from our test suite to improve reliability and ensure tests reflect real behavior.
This change lays the groundwork for future low-code/no-code configuration flows, where the AppConfigContext will become more dynamic and require granular state updates.
How should this be manually tested?
What are the relevant tickets?
A maintainer will add this ticket number.
Resolves VIDSOL-281
Checklist
[x] Branch is based on
develop(notmain).[ ] Resolves a
Known Issue.[ ] If yes, did you remove the item from the
docs/KNOWN_ISSUES.md?[ ] Resolves an item reported in
Issues.If yes, which issue? Issue Number?