Repository navigation
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-5c4e68bb-db66-418c-b814-27707731b4a5 Co-authored-by: tmm <tmm@tmm.dev>
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.
Type-only prototype of component-aware selector completion using a Zyzz-owned catalog and real Base UI 1.8 types. No runtime API or compiler changes.
The TypeScript language-service test verifies Item, Popup, Trigger, side values, nested selector blocks, and unsupported-component behavior. It also demonstrates the structural collision: an unrelated component with the same callback-state shape receives the same hints. Arbitrary CSS selectors remain allowed.
Upstream cooperation could attach an optional type-only attribute schema to each Base UI component export, including attribute value unions. Zyzz could consume that schema instead of matching state shapes, without changing the authoring syntax or adding runtime metadata. The fixture README includes an illustrative declaration and production follow-up requirements.
Validation: completion/consumer checks pass on TypeScript 6, focused TypeScript 7 checking passes, both styleFunction type-bench fixtures pass, and scoped formatting/lint pass. Repository-wide pnpm check:types was killed with exit 137 in this orb and is not reported as passing. No browser behavior is claimed by this type-only experiment.