chore(console): refresh vendored objectui to 23d65c3 (ships #2596 kanban + #2595/#2605 hooks fixes)#3064
Closed
os-zhuang wants to merge 3 commits into
Closed
chore(console): refresh vendored objectui to 23d65c3 (ships #2596 kanban + #2595/#2605 hooks fixes)#3064os-zhuang wants to merge 3 commits into
os-zhuang wants to merge 3 commits into
Conversation
fix(i18n): drop try/catch-around-hook in createSafeTranslation / useSafeTranslate (#2605) objectui@23d65c396b8cd7f4b2a461b187a40e7b384355cd
…es (#2596) Two `board` views that deliberately omit the (spec-optional) kanban binding, so the lane field resolves through the shared stageField detector: - showcase_semantic_zoo (stageField:'status') → lanes Draft/Active/Done with zero view-level config — the objectui#2596 role-driven default; - showcase_semantic_zoo_legacy (stageField:false) → NO default lanes; the pre-#2596 hard-coded 'status' fallback would have grouped by Red/Green. detail-shapes e2e gains the paired assertion (lanes present / lanes suppressed, no page errors on either board). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016wpaFMPowSn4nAWsjeGZib
The two board views didn't resolve via the console's ?view= path (top-level defineView boards don't land in objectDef.listViews and the objects aren't in the app nav), so the browser assertion couldn't reliably verify them. The kanban default-lane behavior (objectui#2596) is already covered by that PR's unit tests plus semantic-roles.dogfood.test.ts (which proves stageField:'status' and stageField:false serve correctly — the exact inputs the console's detector consumes). Keeping only the pin bump. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016wpaFMPowSn4nAWsjeGZib
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Refreshes the vendored
@object-ui/consolepinfb35e48 → 23d65c3soobjectstack dev --uipicks up the objectui range merged since the last bump (#3047) — including this follow-up series' final pieces:stageFieldrole (role-driven lanes;stageField: falsesuppresses default lanes)createSafeTranslation/useSafeTranslatehooks fix…plus the other frontend fixes in the range (inline-edit polish, reference canonicalization, list/dashboard spec-form crashes, Studio CEL editor, etc. — full list in the auto-generated changeset).
Changes
.objectui-sha→23d65c396b8c.changeset/console-23d65c396b8c.md—@objectstack/consoleminor, enumerating the objectui commit range (routed through the same changesets pipeline as backend changes so the frontend delta lands in@objectstack/console's CHANGELOG).Console dist was rebuilt locally at the new pin:
check:console-sha✓ (bundle canary present, dist matches pin), and the existingdetail-shapese2e — the four ADR-0085 detail shapes + the #2577 UX contract — passes 3/3 against the rebuilt console.Note
An attempt to also add browsable
stageFieldkanban dogfood views to the showcase was reverted: top-leveldefineViewboards don't resolve via the console's?view=path (they don't land inobjectDef.listViews, and the semantic-zoo objects aren't in the app nav), so a browser assertion couldn't verify them. The kanban default-lane behavior is already covered by objectui#2596's unit tests plussemantic-roles.dogfood.test.ts(which provesstageField/stageField:falseserve correctly — the exact inputs the console's detector reads). Making those fixtures browsable is a separate showcase-nav change, out of scope for a console bump.🤖 Generated with Claude Code
https://claude.ai/code/session_016wpaFMPowSn4nAWsjeGZib
Generated by Claude Code