Joseph Abrahamson

Hi, I was just informed about this issue and I wanted to plug a library I wrote called [MaiaOrg/haskell-maia](https://github.com/MaiaOrg/haskell-maia). It doesn't seek to be a GraphQL library but instead merely...

Awesome, that's helpful! I had seen that struct behavior happening but didn't realize that it was being caused directly by `->`. That makes sense now, though doubles as a need...

I'd suggest something simple like having it such that if the explicit imports list is on its own line then its formatting is respected (up to name reordering, which I...

I've also been trying to figure this out. I don't see the RUST_SRC_PATH error (maybe getting swallowed) but setting it as above doesn't fix the lack of autocomplete.

It might not be nixpkgs-mozilla, but I can confirm that I've got autocomplete working through lsp-mode in Python, it's just rust-analyzer and rls that are broken. I'll eventually try doing...

Do you think this is a reasonable ticket to send over to `rust-analyzer`? It might not be a priority of theirs, but handling symlinks when searching for source files seems...

- My design so far was to have the user specify options at each leaf node where options are available. We could attempt to do it all in one go...

Oh, as in I'm not personally motivated to have `Options` bear the whole HATEOAS burden. It just needs to do CORS. My understanding is that what you'd want in an...

So I have a partial expanded design which includes room for some CORS. It's kind of nice but I'm a little stuck on the type level stuff in one part....

This is mostly a POC again, btw. To really specify this correctly we need to differentiate between _analysis_ which should be totally automated and CORS which is up to the...