Ryan Johnson

I could see this syntax being helpful for _custom_ composite tokens. However, it doesn't provide any additional value for composite types that are already _part_ of the spec. Spec-defined, standard...

> What if you want to describe line height in typography as `"10px"` and as `1.2`. Currently those are two different types, a `dimension` and a `number`. In this case,...

The problem with disallowing custom properties on JSON objects is that you break the entire spec, because any JSON object property that doesn't begin with `$` is thus invalid. This...

> It's interesting what you say about the React support being very close to what you would need @CITguy. It sounds like if we had the ability to support plain...

Thoughts on API... ## Define Namespace `CSS.selectorNamesapces.define( name )` * returns: `CSSSelectorNamespace` object (see below) ```javascript /* create a namespace for prefixed selector definitions */ let fooNs = CSS.selectorNamespaces.define('foo') //...

One thing I can't do is a "default" fallback for when a property has multiple values. Currently, I have to negate all other values to get a "default" / fallback...

# Conditional blocks Say I have a Button component with the following setup... ``` Button - iconOnly:boolean(false) - label:string('button') - iconLeft:instanceSwap - iconRight:instanceSwap ``` the following table illustrates which props...

> Ah, this is because we run plugin code in a javascript VM (here's a [link to our blog post ](https://www.figma.com/blog/how-we-built-the-figma-plugin-system/) about it if you want to learn more!), so...

> I tend to be in favour of more rigid specs to keep developers accountable, and therefore would not be in favour of this change. Developer accountability shouldn't be the...

## Environment _(FYI: I'm unable to upgrade Flutter/Dart due to business constraints.)_ * Flutter: 3.32.8 * Dart: 3.8.1 * DevTools: 2.45.1 * pubspec.lock * widgetbook: 3.19.0 * widgetbook_annotation: 3.8.0 *...