Yaroslav Petryk
Yaroslav Petryk
Also added a test to make sure the intended behaviour for this typename optionality, explained [here](https://relay.dev/docs/next/guided-tour/updating-data/imperatively-modifying-linked-fields/#example-assigning-to-an-interface-when-the-source-is-not-guaranteed-to-implement-that-interface), is not broken by me or anyone else.
This looks like a more overarching inability of linaria to work with "virtual modules", or transforms applied by the build pipeline in general (assuming your transformations are not done with...
Oh, thanks @indianakernick. Turns out `'foo' | S` was the missing key in my case. Couldn't think, by myself, of how to require a transaction has selected at least the...
Similar issue is also present with `@radix-ui/react-toolbar`
Well, yeah. I have two solutions. 1. Just don't use namespace imports, import all of the named components. This way the import gets tree-shaken away. Yeah it's tad a bit...
For me the issue is not the presence of a BE/datastore but the privacy concerns of collecting user data (possibly without their permission). Doing so anonymously is crucial, yet the...
This is an easy thing to do. I can draft a PR, but would mostly like to judge feedback if this is something we are willing to pursue
> in your application you could technically just ignore/discard the `'off'` Yes, right now I do discard the `'off'` values. It is somewhat unintuitive though for cases where a set...
Can confirm the behavior is the same in 1.9.0-rc.0