Iha Shin (신의하)
Iha Shin (신의하)
PoC done, maybe we could release this pretty soon?
How about just adding an optional argument to `.exhaustive()` that works as same as `.otherwise()`? So just like: ```ts declare const input: 'a' | 'b'; const mode = match(input) .with('a',...
It can move non-frame block. so you should change your elevator's design.
That sounds reasonable. I'll look into it
Done! Can you review the changes again @kwonoj
I'd also like to have Relay LSP support (which is done by an extension in VSCode) which can be utilized by calling the Relay compiler binary with the `lsp` command...
It looks like not having a well-maintained Tree-sitter parser for GraphQL is the biggest blocker right now, since the official GraphQL syntax extension for VSCode is based on TextMate grammar
I wonder if it'd be possible to support UnoCSS transformer features like [variant groups](https://unocss.dev/transformers/variant-group)...
It's because of using raw source strings to determine the object access overlap: [source](https://github.com/biomejs/biome/blob/02747d76ebfc8775e700a7fa5517edcb24fcabeb/crates/biome_js_analyze/src/semantic_analyzers/correctness/use_exhaustive_dependencies.rs#L585-L592) I'd like to contribute on this one.
I know that setting the value to `true` resolves the issue, but that's not the point. It's clearly an unexpected behavior that the resource gets stuck forever without any errors....