File: packages/cli/templates/blocks/components/Selector/SelectorShowcase.tsx
Problem: The main Selector showcase rendered on the docsite is a controlled component with no state. It passes no value and a no-op onChange={() => {}}, so choosing an option never updates the displayed selection — the selector appears broken. More noticeable on touch/mobile.
export default function SelectorShowcase() {
return (
<Selector
label="Fruit"
options={['Apple', 'Banana', 'Orange', 'Mango', 'Pineapple']}
placeholder="Select a fruit..."
onChange={() => {}}
/>
);
}
Expected: Wire local state like the other Selector examples (SelectorClearable, SelectorWithSections, etc.) already do:
const [value, setValue] = useState<string | undefined>();
return <Selector label="Fruit" options={...} value={value} onChange={setValue} placeholder="Select a fruit..." />;
Note: This is NOT a component bug or a mobile-responsiveness bug — it's the showcase example not propagating state.
Reported via external user feedback relayed through Astryx (an X commenter testing on mobile).
File:
packages/cli/templates/blocks/components/Selector/SelectorShowcase.tsxProblem: The main Selector showcase rendered on the docsite is a controlled component with no state. It passes no
valueand a no-oponChange={() => {}}, so choosing an option never updates the displayed selection — the selector appears broken. More noticeable on touch/mobile.Expected: Wire local state like the other Selector examples (
SelectorClearable,SelectorWithSections, etc.) already do:Note: This is NOT a component bug or a mobile-responsiveness bug — it's the showcase example not propagating state.
Reported via external user feedback relayed through Astryx (an X commenter testing on mobile).