Discussion:
Elm Language Server - Document and repository to coordinate and capture requirements effort
(too old to reply)
Håkon Rossebø
2017-09-07 13:21:28 UTC
Permalink
(Also posted in elm-dev) Based on previous discussions and my own
experience from the vscode-elm extension, having a common language server
can help improve editor support and tooling features. Currently, many
editor extensions use their own parsers to support a common set of features.

I've created a repository with issues and a requirements document to
capture and discuss any features here -
https://github.com/hakonrossebo/elm-language-server-requirements-specification

In this document, I've also tried to collect links to all previous
discussions and reference implementations.

I hope this repository can help improve the coordination of effort to
improve editor and tooling support.

This is just the initial work. Please suggest any improvements in the
repository issues or create PRs for the requirements document.
--
You received this message because you are subscribed to the Google Groups "Elm Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Roman Frołow
2017-09-08 18:42:13 UTC
Permalink
Good, by why have a document outside of a git repository?

Markdown is quite good for that and you can have precommit hook to generate
toc
--
You received this message because you are subscribed to the Google Groups "Elm Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Håkon Rossebø
2017-09-12 07:52:56 UTC
Permalink
I considered both alternatives and actually started with only a markdown
file on the repository. After some initial discussions, we landed on a
separate Google Document for now, making it easier to write and comment
directly for all. This can be changed back to a markdown document at any
time if more people suggest this as a better alternative. Join in on the
#elm-langauge-server Slack channel to discuss.
Post by Roman Frołow
Good, by why have a document outside of a git repository?
Markdown is quite good for that and you can have precommit hook to
generate toc
--
You received this message because you are subscribed to the Google Groups "Elm Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Vlad GURDIGA
2017-09-09 09:04:26 UTC
Permalink
This seems a lot like the thing that I have found unusually useful in
TypeScript land: tsserver
<https://github.com/Microsoft/TypeScript/wiki/Standalone-Server-%28tsserver%29>.
Looking at that case, it seems like a language server would make for much
more streamlined efforts around the language tooling, IMHO. 🀔

Just my little 2¢. 🀓
--
You received this message because you are subscribed to the Google Groups "Elm Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...