crystal-lang-tools/lsp

Crystal implementation of the Language Server Protocol

lsp's Issues

LICENSE file not carried over from scry

So far, this library is just a dump of code pulled out of the scry repository, but the LICENSE file was not copied.

The original copyright line

Copyright (c) 2017 Ryan L. Bell and Contributors

must be retained instead of or alongside the new copyright line

Copyright (c) 2018 Kepler Sticka-Jones

If this is not done, then this repository is in violation of the original MIT license for the code.

I'm sure this was just an unintentional mistake / oversight, but since I'm forking this library to make some improvements (that I hope to eventually contribute back!) I wanted to make sure that everything was "on the level" with the copyright license.

Add spec

Add spec, something like parsing json examples using protocol specifications

Porting code to JSON::Serialization + add Client side structs

Hi,

I'm using this shard to implement the client side of LSP on my project (Tijolo), so I added few missing structs and some constructors needed, plus ported the structs I used until now to JSON::Serialization. All this is unorganized in my fork in a single commit. If there are interest, I can submit PRs with the changes, but I would like how do you guys like the PRs to be organized... one per struct, one with just JSON::Serializable changes and other with new structs, etc...

Also.. I'm porting the structs when I start using them, so the project will be in a state where half structs will be using JSON::Serializable and other half using JSON::Mapping.. anyway, better than have all using the deprecated API as it's now.

Support full LSP specification

Add support for all protocol specifications.

Ref: https://microsoft.github.io/language-server-protocol/specification

This shard can be used by other languages and tools like ameba, amber, lucky, etc

/cc @veelenga, @eliasjpr, @elorest, @drujensen, @paulcsmith