Uh oh!
There was an error while loading. Please reload this page.
fix(app-shell): warn when userFilters on an object list view is suppressed - #2220
Merged
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
Uh oh!
There was an error while loading. Please reload this page.
…essed (#2219) ADR-0053 reserves userFilters/quickFilters for page lists and suppresses them on the object default list ("views" mode). The suppression is correct but was completely silent, and the phase-4 guardrail (zod refine + check rule) that should catch the wrong-context authoring error hasn't landed — so authors got a valid schema and a page rendering nothing where their filter controls should be. Emit a one-shot console warning per object/view naming the offending fields and where they belong. Fixes#2219 Co-Authored-By: Claude <noreply@anthropic.com>
…views-mode # Conflicts: # packages/app-shell/src/views/ObjectView.tsx
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.
Fixes#2219
Problem
ADR-0053 (views mode vs filters mode) correctly suppresses
userFilters/quickFilterson the object default list —packages/app-shell/src/views/ObjectView.tsxhardcodes them toundefinedinrenderListView. But the suppression is completely silent, and the ADR's phase-4 guardrail (zodrefine+checkrule rejecting the wrong-context field) never landed:packages/types/src/zod/objectql.zod.tsstill acceptsuserFilterson any list view with no context check.Net effect: an author (human or AI) who puts
userFilterson an object list view gets a schema that validates, a build that passes, and a toolbar with nothing where the filter dropdowns should be — zero signal at any layer. Found while dogfoodingapp-showcase(showcase_task.tabularcarries exactly this wrong-context block).Fix
New
warnSuppressedListNav()util, called fromrenderListViewright before the suppression: when the view def or base list schema actually carriesuserFilters/quickFilters, log a one-shot warning (per object/view) naming the offending fields, the ADR, and where the fields belong (InterfaceListPage "filters" mode). Same "never swallow silently" treatment as #2217/#2218.The suppression itself is untouched; the phase-4 schema-level rejection can supersede this warning when it lands.
Testing
pnpm --filter @object-ui/app-shell... buildpasses.app-showcasebackend): openingshowcase_task.tabular— whose metadata carries a wrong-contextuserFiltersblock — now logs[ObjectView] View "showcase_task.tabular" on object "showcase_task" defines userFilters, which are ignored on an object list view (ADR-0053 "views" mode …).🤖 Generated with Claude Code