fix(detail): inline-edit enrichment passes min/max/step; live e2e for the #2572 polish set#2615
Merged
Merged
Conversation
…ive e2e (#2572) Live dogfood follow-up to the #2572 polish (PR #2604): DetailSection and HeaderHighlight enrich the field they hand InlineFieldInput from an explicit whitelist of objectSchema keys, and that list dropped the numeric range/step constraints — so a currency field declaring min: 0 rendered its number input with no min/max/step. Both enrichments now pass min/max/step through. Also adds e2e/live/inline-edit-polish-2572.spec.ts, a live spec driving the whole #2572 polish set against the real showcase stack (expanded-lookup passthrough with zero hydration fetches, currency min/step, header Edit CTA disable, Esc/Ctrl+Enter, and the approval-lock preflight via the showcase_budget_approval flow). Verified green end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JQjNZDdqmz2QHGQndpjZrR
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang
marked this pull request as ready for review
July 16, 2026 14:53
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 free
to 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.
Live-dogfood follow-up to #2572 / PR #2604, found by driving the merged polish on the real showcase stack (console dev
:5191+framework/examples/app-showcase).Fix: numeric constraints were dropped by the field enrichment
DetailSectionandHeaderHighlightenrich the field they handInlineFieldInputby copying an explicit whitelist of objectSchema keys (type, options, currency, precision, scale, format, reference…).min/max/stepwere not in that list — so although #2604 taughtNumberField/CurrencyFieldto surface them, the showcase Project.budget (currency,min: 0) still rendered its number input with no range constraints, because the metadata never reached the widget. Both enrichments now passmin/max/stepthrough (unit tests added; the DetailSection one pinsmin/max/stepon the rendered spinbutton).New: live e2e spec for the whole #2572 polish set
e2e/live/inline-edit-polish-2572.spec.tsdrives all five items end-to-end against the real stack and is green:findOnefetches;showcase_budget_approval(verifiedpendingvia the approvals API), and on reload every pencil/double-click affordance is gone and double-click no longer opens a session (note: this backend does not materializeapproval_statuson the record, so the lock engages via the pending-request branch ofapprovalLocked— with the field-only signal it would never lock);input[type=number][min=0][step=0.01];The run also flushed out a framework bug: the default CORS allow-list omitted
If-Match, so every split-origin inline-edit save failed preflight with "Failed to fetch" — fixed separately in framework PR objectstack-ai/objectstack#3067 (the spec was verified green against that fixed stack).Known cosmetic gap (pre-existing, not addressed here):
DetailView's "Locked for approval" band keys offrecord.approval_statusonly, so on backends that track the lock purely via approval requests the band never shows even though editing is correctly locked.Verification
plugin-detailsuites green locally (DetailSection.inlineEdit + HeaderHighlight.editable: 10/10).:4022(with the framework CORS fix) + console dev:5191.🤖 Generated with Claude Code
https://claude.ai/code/session_01JQjNZDdqmz2QHGQndpjZrR
Generated by Claude Code