Repository navigation
[WIP] Enhance visual appeal of examples in studio - #29
Merged
Merged
Conversation
Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
Copilot stopped work on behalf of
huangyiirene due to an error
January 14, 2026 13:30
Contributor
|
@copilot 继续，优先处理这个任务 |
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
Contributor
Author
已完成优化任务！我对studio中的examples进行了全面的视觉优化： ✅ 已完成的优化：
所有JSON文件已验证并成功构建。(Commit: e166f7a) |
Contributor
|
✅ All checks passed!
|
hotlong
marked this pull request as ready for review
January 14, 2026 14:09
Copilot stopped work on behalf of
hotlong due to an error
January 14, 2026 14:10
This was referenced Sep 4, 2026
This was referenced Sep 4, 2026
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 9, 2026
…e header teaching a retired filter (objectui#7513) (objectstack-ai#7617) Tightens precision rule 4 of `check:spec-symbols` from symbol to member granularity, per the maintainer ruling of 2026-09-04 (batch objectstack-ai#29, A′ + b). A comment citing `SpecSymbol.key` where the spec's own shape has no `key` is now a dangling reference. Three measured specimens took that shape and all three were inviting a 422: `SelectOptionSchema.description` (twice, into a `.strict()` option schema, which sinks the whole field), `FieldSchema.rows`, and `DashboardSchema.title`. Every one of them named a symbol the spec really exports, so rule 4 passed them. This is rule 4 tightened, not a second instrument: no allowlist and no ledger of its own — the measured population is 0 on this commit, so a hit is always fresh and fails on the PR that writes it. Zod's own API is excluded by two documented predicates (call form, plus a five-name introspection vocabulary), never by allowlist entries. Also corrects the two header paragraphs that still described the `export`-modifier filter in the present tense, beside a `hasExportModifier` helper that had lost its last call site. A card was filed on the strength of that prose; the helper is removed so nothing is left to grep into the same false conclusion. Claude-Session: https://claude.ai/code/session_01KbJQ1y1J12nZxYzFWhP8Q3 Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 9, 2026
…rfaces (objectstack-ai#7622) The five dashboard-ROOT `title` read arms retire together under ADR-0049 (objectui#7509, maintainer ruling 2026-09-04, decision batch objectstack-ai#29, option C). `label` — REQUIRED on `@objectstack/spec`'s `DashboardSchema` — becomes the only header source, then the raw `name`. `DashboardSchema` refuses a root `title` BY NAME (`unrecognized_keys(title)`) and the save route answers 422, so no authored document can acquire the key; what retires is compatibility with documents stored before that refusal. Five surfaces read the legacy spelling independently, so one stored document could show one header in the console and a different one in the designer — which is why the ruling refused retiring any single arm. Widget-level `widget.title` (`DashboardWidget.title`, the spec's `I18nLabel`) is a different DECLARED key and is untouched; root and widget arms were separated by receiver, not by grep, and every pin carries a widget control. Each arm gets a refusal-shaped pin in the objectstack-ai#5830 / objectstack-ai#5852 form. Two existing pins asserted the retired behaviour and were rewritten rather than deleted: `dashboardAuthoredInputs`' "the legacy `title` read stays" block (its objectstack-ai#5742 exclusion of `title` from published inputs is unchanged) and `DashboardGridLayout.inlineLocaleLabel`'s precedence case. Claude-Session: https://claude.ai/code/session_01KbJQ1y1J12nZxYzFWhP8Q3 Co-authored-by: Claude <noreply@anthropic.com>
This was referenced Sep 24, 2026
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.
Plan: Optimize Studio Examples for Visual Appeal
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.