Wasp lang dev tooling

[craigmc08]

This issue organizes all issues and features relevant to dev tooling for the wasp language.

Wasp Analyzer

• [ ] #687
• [ ] #686
• [ ] Update typechecker so it can run on wasp source code containing syntax errors in it
• [ ] Update typechecker to be able to report multiple type errors
• [x] Check if ExtImport paths exist

waspls

• [X] Merge waspls cabal project into the waspc cabal project #709
• [X] Bundle waspls with waspc installation #709
• [ ] Implement semantic highlighting in the language server
• [ ] Improve autocompletion results
  • [ ] Add enum values to the results
  • [ ] Use expected type for the cursor location to filter results
  • [ ] Dictionary field completion
• [ ] Implement more LSP features
  • Potential priority list: go-to-definition for wasp objects, go-to-definition for external imports, rename wasp objects
• [ ] Show AppSpec validation errors in LSP diagnostics

JS/TS Intellisense

• [X] For the best effort/reward ratio here, we should focus on getting TS support for wasp projects. This is a highly requested feature and will also pave the way for getting TS intellisense to work since the TS compiler will understand how wasp projects work a little bit by then.

VSCode extension

• [ ] Code formatting for wasp files
• [ ] Find a way to keep current syntax highlighting in sync with wasp language
  • With no semantic highlighting (yet), we have a textmate grammar defined in the vscode extension. This manually lists out all object types and enum values, which means we need to keep those lists in sync with wasp type definitions. Maybe we can find a way to keep this in sync automatically.

[Martinsos]

Regarding JS/TS intelissense in user created files in ext-src/ -> we explored this a lot in https://github.com/wasp-lang/wasp/issues/604 . We kind of concluded that the best solution for now might be to "explain" to editor via jsconfig.json and by possibly adjusting position of some of our genreated files so that it all "looks good" to the editor and that JS/TS IDE can mostly work on stuff then.

[Martinsos]

It would make sense to also include AppSpec validation errors into LSP. Right now those are not made a part of it. Only analysis is done, but app spec validation is not. We would want to do it and show those also.

[Martinsos]

Also, it would be great if Wasp compiler would inform me about wrong ext/ import paths! It could check during compile time if those exist.

[Martinsos]

Another thing: It would be great if we could get Wasp LS to the level where it offers autocompletion for dictionary fields! Right now it doesn't do that.