Kim Ode

Nice! I think it would also be worthwhile to run `(executable-find "unzip")` first, since this will be installed on some Windows systems that use Emacs. Some users will have unzip...

Could you point me in the direction to where you applied that hack? I could problaby figure something out if I just knew where to look.

Great, thanks! In case anyone else is wondering, I simply filtered the semantic errors in CodeCheckHandler.cs like this: 

It would be nice to have a setting to ignore code issues messages. Also they should problaby be shown as warnings, not errors. I made a quick fix for that...

Thanks! Should I close this and create a new issue in omnisharp-server?

Yeah, this isn't great. I haven't run into this yet because we only use getQueryClient in external stores. Maybe we can solve it on the type level somehow.

I had a similiar problem today, and it's possible to type the root store with a view. (Typing the actual query client seems more difficult.) ``` ts // RootStore.ts export...

Draft pr here: https://github.com/ConrabOpto/mst-query/pull/33

Now available on npm as `2.0.0-alpha.1`. Remaining work: - [ ] Enabled-prop - [ ] React 18 & Suspense - [ ] Invalidating queries The two last items might happen...

React 18 does seem to require a re-think of the api somewhat. A mutable object cannot reliably be stored in a useState hook, it needs to be external to react....