Uh oh!
There was an error while loading. Please reload this page.
refactor: remove view-level tabs; userFilters is the sole page filter (ADR-0053) - #1804
Merged
Conversation
…age filter (ADR-0053)
Validated against Airtable's Interface Designer: "User filters" (None/Tabs/
Dropdown) is the end-user filter control; a tab is just {name, filter} and never
switches the view form (that's "Visualizations", a separate axis). ObjectUI's
schema.tabs carried a "view" switch, conflating filter and form, so it is removed:
- types: drop ListViewSchema.tabs
- plugin-list ListView: remove activeTab state, mount tab-filter effect,
handleTabChange, the TabBar/TabBarSelect render row; simplify the
mutually-exclusive guard to filterElements = userFilters
- plugin-view ObjectView: stop passing tabs through
- app-shell ObjectView: drop the tabs:undefined suppression
- react spec-bridge: stop mapping spec.tabs (clean-build; check rule flags it)
- TabBar component kept (still used by plugin-view's view switcher)
- tests: remove schema.tabs "tabs rendering" suite; userFilters tabs tests stay
Full monorepo type-check 58/58; affected tests 197 pass. Browser: object list
shows one switcher row, no legacy tab row, list loads.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Part of ADR-0053. Retires mechanism #3 (the view-level
schema.tabs/TabBar).Why (validated live against Airtable)
Airtable's Interface Designer separates User filters (None / Tabs / Dropdown — the end-user filter control; a tab is
{name, filter}) from Visualizations (List / Timeline / Kanban — the view form). A tab filters data, never switches the view form. ObjectUI'sschema.tabscarried aviewswitch, conflating the two → removed.userFilters(dropdown | tabs) is the single page-filter mechanism, matching Airtable.Changes
ListViewSchema.tabsListView: removeactiveTabstate, mount tab-filter effect,handleTabChange, theTabBar/TabBarSelectrender row; simplify guard tofilterElements = userFiltersObjectView: stop passingtabsObjectView: drop thetabs: undefinedsuppressionspec.tabs(clean-build; acheckrule flags it later)TabBarkept (still used by plugin-view's view switcher)schema.tabssuite;userFilterstabs tests untouchedVerification
type-check 58/58; affected tests 197 pass. Browser (showcase): one switcher row, legacy
view-tabsrow gone, 10 records load, no errors.🤖 Generated with Claude Code