Brian Heston

> Philosophically, I'd suggest the value comparison method is intrinsic to any control which matches user-typed input to pre-defined values in a component I support this, in the same vein...

> @bheston, after digging further, A single `valueComparer` function wouldn't work, because `filterOptions` uses a `startsWith` comparison, instead of equality. I could conceivably add a more defined type for this...

I tested the width issue in Storybook by manually adding `width: 500px` to each host element and found no issues. Hopefully that was the problem, either way there shouldn't be...

I'm sorry I missed the issue you opened for this, or I would have provided this feedback then. The main concern here is complicated by the history of poorly designed...

While I find this updated structure interesting, I'm not sure it resolves some of the fundamental issues we've had around working with tokens. As I've been actively implementing about three...

I mention the Adaptive UI points not to complicate this issue, but because the work is very much related. I understand we can improve the performance and usability of the...

> > Having a container for tokens (the `system`) is imperative. > > @bheston can you clarify this for me? Does this mean that having a DOM Element as a...

@janechu These sound like different things. The goal of the design surfaces was to function more like traditional design software than devtools. A general css editor should be paired with...

I've come across another place I'd like to use this model, which is that some components have different presentations. For instance, a component often referred to as a "segmented control"...

Which node version are you running? I'm on 18.17.1 on Windows and it's been working when I run `npx` from within VSCode. Maybe they changed it in v20?