Diya 🔥 fix(toggle): Fixed Toggles on Weekly Summary Report#5339
Merged
Conversation
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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
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.



Description
Fixes two UI regressions on the Weekly Summaries Report page: the Bio announcement toggle was rendering as raw text "postedrequested" with no interactive control visible, and the Bio Status filter toggle had no visual distinction between its on/off states.
Related PRS (if any):
None
Main changes explained:
How to test:
Screenshots or videos of changes:
Before:


After:


Note:
The root cause of the bio toggle regression was a bad import that replaced the TriStateToggleSwitch React component import with a CSS file import — likely introduced during a refactor or merge conflict resolution. No backend changes required.