Skip to content

finding(types): object-grid and list-view conditionalFormatting still accept the native { field, operator, value } rule and top-level colour keys the spec's list-view rule refuses ("migration deferred") #11533

Description

@objectstack-fleet

Filing-gate category: ① a defect, finding class: two doors over one contract disagree. The authoring faces here accept a rule dialect the spec's own member refuses.

Direction (for triage, not a ruling)

objectui#11522's ruling 5963861071 (retire, not widen; zero measured pull for a second spelling) is the family's precedent. The "migration deferred" comment is the only stated reason the grid and the list view keep the native rule. ⛔ Never widen the spec's list-view member to the native rule.

Dedupe

The 1,000 most recently updated objectui issues and PRs, open and closed, back to 2026-09-25 (REST, grepped locally 2026-10-03):

Dedupe words: object-grid conditionalFormatting native rule · ListViewSchema conditionalFormatting broader than spec · grid rule dialect spec bump


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:recordsBusiness objects, records, the views that show data, usable forms, searchbugSomething isn't workingdomain:specobjectui spec stream: fix lands on packages/types, schema corpus or spec pin coupling — spec lanepriority:p2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions