[Feature Request] Language Server Protocol

[keplersj]

For easier editor integration the Language Server Protocol can be used for lint tools like this.

See:
VSCode's TSLint LSP Server
VSCode's ESLint LSP Server

For Scry we have a Crystal implementation of the protocol, and I believe that this would be a very good reason to modularize it as a lsp shard.

/cc @faustinoaq

[veelenga]

I don't think Ameba should have its own implementation of lsp or depend on it. The tools like Scry (which already implements LSP) can just use Ameba. Just the same way like Scry already uses Crystal.format and crystal build tools.

Instead, it seems to be a question of a data format. Ameba uses Formatters for a different kind of output formats. For example, this emacs plugin depends on a FlycheckFormatter.

So we can add a new formatter suitable for the needs of Scry or other LSP implementations.

[veelenga]

Here is an example of how this works in ruby together with Rubocop:

https://github.com/mtsmfm/language_server-ruby/blob/2349981fbd625038bd55333d39caa3646dcad987/lib/language_server/linter/rubocop.rb

I am going to add JSON formatter #38. Anyway, it was planned to be added to let it be usable with ale.