fix(ui): don't use anti-pattern in CheckboxFilter #11739
Merged
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.
Fixes #11686 (comment)
Motivation
Per my review, fix: cron workflow initial filter value. Fixes #11685 #11686 used an anti-pattern of setting a prop based on another prop
CronWorkflowsList
now roughly matches howWorkflowsList
sets its initial state (it also useslocalStorage
& query params though)refactor
CheckboxFilter
to be a functional component8.
as wellModifications
ChekboxFilter
logic to instead set the initial state to have all phases in the top-level component,CronWorkflowList
, as I suggested in my review commentCheckboxFilter
to a functional component as mentioned aboveVerification
/cron-workflows
state
andprops
change as expected./workflows
and confirmed that it works as before and no behavior was changed.See below screenshot of
/cron-workflows
with React DevTools open showing theCheckboxFilter
props:Future Work
This component may be possible to further simplify and optimize:
<React.Fragment>
seems unnecessaryI didn't change these as I wanted to keep this PR/diff relatively clean