Skip to content

Update editor and tooling support #347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 6, 2020
Merged

Update editor and tooling support #347

merged 3 commits into from
Sep 6, 2020

Conversation

thomashoneyman
Copy link
Member

Relates to #343 and closes #274. This merges the contents from the Recommended Tooling for PureScript Applications in 2020 post on Discourse into the editor and tooling support post.

It's somewhat of an overhaul of the existing documentation page, but I believe the new version accomplishes a few goals:

  1. It makes it clear right away what the minimum recommended tools are for a typical PureScript project
  2. It emphasizes Spago as the default choice for package management and build tooling
  3. It includes tools from the PureScript ecosystem which are useful for developing libraries and applications that are not only for use with editors.
  4. It mentions necessary tools when integrating with another ecosystem for a particular backend (namely, JavaScript tools for projects which integrate with JS).

This documentation could be narrowed to only include build tooling and editor tooling, but I think it's sensible to include things like setup-purescript, zephyr, and purty here -- they're useful for development generally and there's not really a place for them elsewhere in the documentation at the moment. We could move them elsewhere later on.

I moved the gulp-purescript task to the deprecated section because that tool has been deprecated.

@hdgarrood
Copy link
Collaborator

Looks great! I have a very minor nit that we should be avoiding "psc" now since the compiler executable no longer uses that name; I think the IDE server built into the compiler should ideally be referred to as purs ide server to minimise the risk of confusion. The editor plugins which include "psc-ide" in their names probably should be referred to by their actual names still, of course.

@thomashoneyman thomashoneyman merged commit 31e1624 into purescript:master Sep 6, 2020
@thomashoneyman thomashoneyman deleted the patch-1 branch September 6, 2020 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add recommended tooling for PureScript applications
3 participants