Support PureScript's new spago.yaml configs #9362
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PureScript's rewritten package manager / build system, spago@next, has moved from
spago.dhall
tospago.yaml
config files.When purescript-language-server is launched in a directory that does not appear to be a PureScript (spago) project, it tries to ask the user to resolve this issue. In Helix, this causes purescript-language-server to exit immediately:
This change adds support for new
spago.yaml
config files as PureScript project roots, which enables purescript-language-server to launch without issue for spago@next projects.