Uh oh!
There was an error while loading. Please reload this page.
feat(studio): surface the enable.searchable toggle in ObjectSettingsPanel - #2801
Merged
Conversation
…anel (#2800) framework#2377 corrected enable.searchable to LIVE — the Global Search executor gates on it (explicit false opts the object out of cross-object search) — leaving it the only live enable.* flag the Studio settings panel did not expose. Render it as an opt-out toggle (spec default true) between activities and clone, mirroring the other opt-out flags. - CAPABILITIES entry + updated header/inline comments (no more 'not yet surfaced here') - en + zh i18n keys; the description routes field-level match config to searchableFields (ADR-0061) so the whole-object opt-out isn't conflated with per-field search settings - Tests: cap-searchable presence + default-checked + authored-false reflection; trash/mru absence guards stay - Changeset: @object-ui/app-shell minor ObjectSettingsPanel (12) + studio-locale i18n tests green (17 total). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RRCHNGhKw8uVhA3ghXKDpA
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 24, 2026 14:02
Uh oh!
There was an error while loading. Please reload this page.
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.
Implements #2800. Follow-up to #2799 / framework#2377.
enable.searchablewas corrected to LIVE during framework#2377 — the Global Search executor gates on it (packages/metadata-protocol/src/protocol.ts:2967in framework), so an explicitfalseopts the object out of cross-object search. That left it the only liveenable.*flag the Studio settings panel did not expose.Changes
ObjectSettingsPanel.tsx:searchablerenders as an opt-OUT toggle (spec defaulttrue, explicitfalsedisables), placed betweenactivitiesandclone; header/inline comments updated (no more "not yet surfaced here").capSearchable"Global search (searchable)" / 「全局搜索(searchable)」. The description deliberately routes field-level match configuration tosearchableFields(ADR-0061) so the whole-object opt-out isn't conflated with per-field search settings — the wording concern flagged in Studio: surface anenable.searchabletoggle in ObjectSettingsPanel (flag is LIVE — global-search opt-out) #2800.cap-searchableflips from absence to presence + default-checked; the authored-values test now also coverssearchable: false;cap-trash/cap-mruabsence guards stay (they protect against authoring keys the strict spec schema rejects).@object-ui/app-shellminor.Verification
ObjectSettingsPanel.test.tsx(12) +studio-locale.i18n.test.tsx— 17 passed locally.Closes#2800
🤖 Generated with Claude Code
https://claude.ai/code/session_01RRCHNGhKw8uVhA3ghXKDpA
Generated by Claude Code