Content
View differences
Updated by Mir Bhatia 4 days ago
Currently, there are some differences in the way filters behave as a quick filter and when visible in the expanded "All filters".
**Acceptance criteria**
* Filters visible as quick filters and in "All filters" should behave the same way
* In cases where they differ right now (meetings index page only, since it's the first use case), update "All filters" to match the quick filter implementations
* SegmentedControl and Boolean quick filters should not be removable in the "All filters" section, as this results in an ambiguous state (since they cannot be made inactive via the quick filters)
* "All filters" equivalents of SegmentedControl or Boolean quick filters need to be single select
* The same options should be visible for SelectPanel quick filters and their equivalents in "All filters" (eg, in the meetings index page, the project quick filters only shows projects that have meetings visible, but in the "All filters" section, any project visible to a user is select able)
* There should be component level guards/patterns in place to make this harder to miss for further quick filter implementations
**Acceptance criteria**
* Filters visible as quick filters and in "All filters" should behave the same way
* In cases where they differ right now (meetings index page only, since it's the first use case), update "All filters" to match the quick filter implementations
* SegmentedControl and Boolean quick filters should not be removable in the "All filters" section, as this results in an ambiguous state (since they cannot be made inactive via the quick filters)
* "All filters" equivalents of SegmentedControl or Boolean quick filters need to be single select
* The same options should be visible for SelectPanel quick filters and their equivalents in "All filters" (eg, in the meetings index page, the project quick filters only shows projects that have meetings visible, but in the "All filters" section, any project visible to a user is select able)
* There should be component level guards/patterns in place to make this harder to miss for further quick filter implementations