Jon Bockhorst
Jon Bockhorst
It's happening to me on windows, both when connecting to a separate machine, and the same one.
Maybe we have to convert the uris from the vscode client using https://www.npmjs.com/package/vsls
No, I had to "unfix" this. The type inference is technically correct in this case, but it can maybe be rendered different because of the aliases. It's not a simple...
Specifically, here (unparseable elm.json): https://github.com/elm-tooling/elm-language-server/blob/003ede17fc99ae22fd04f5bdcbc059f2c14d1a98/src/elmWorkspace.ts#L719 and here (unsolvable dependencies): https://github.com/elm-tooling/elm-language-server/blob/003ede17fc99ae22fd04f5bdcbc059f2c14d1a98/src/elmWorkspace.ts#L507 are 2 places we can report diagnostics in the `elm.json`
* CompletionItem `labelDetails` would be good for adding type annotations and file names to completions * We should explore any good uses for inlay hints * Explore the new diagnostics...
We should be able to get the operator import in the current source file from `IImports`, which would ensure it is actually imported. Then the we can build the cache...
Should note that this is the behavior in intellij as well.
This tool is really helpful and I agree that it should be a part of tree-sitter, as it makes working with TypeScript much better.
Yeah I just missed it in the commit. It's there now.