Ian Copp

Similar to a configuration setting for this would be something to tell Prettier what parser any given tagged template literal should use. I'm using AngularJS in template literals, for example.

I feel like the best thing to do here would be to follow the lead of ISO, which for country code uses deprecation warnings (but doesn't remove from the dataset)...

That makes sense, but also makes me think that there's missing functionality there on `Box`. Of course, that's probably more suited to wait until after borders go on so any...

Not that I can speak for anybody else, but I'd personally prefer something with the confidence processing gone completely (or at least with an option to disable it) in favor...

My general thoughts: A two-pane layout. - The left pane has a tree view with re-sortable elements. I'm imagining the left pane of browser bookmark managers for the look here....

This makes me think of something where contexts effectively become a new evidence source, and the current workflow of `evidence -> rule -> context -> action` becomes `evidence -> rule...

I've repeatedly run into this problem while trying to do bulk operations on `auth.api.getUser` / `auth.api.createUser` to synchronize a new Supabase project with a (for now) external source of truth...

Any chance this will get merged anytime soon?

For the project I'm currently working on, we've leaned heavily on leaving items `undefined` where possible (though Redux gets in the way of that somewhat) because (a) we're using `react-redux`...

For this case, you don't want an `outDir` at all. The actual build/compile is all handled by Webpack. I'll see about adding more explanatory stuff, but it'll take updating things...