Skip to content
This repository was archived by the owner on Dec 29, 2022. It is now read-only.

jsonrpc conformance #62

Closed
chergert opened this issue Oct 20, 2016 · 4 comments
Closed

jsonrpc conformance #62

chergert opened this issue Oct 20, 2016 · 4 comments

Comments

@chergert
Copy link

I was starting to put together a jsonrpc and language server plugin for GNOME Builder and discovered that ls_service.rs seems to require the "id" field be an integer. According to what I've read so far on JSONRPC (which is very little) I believe it should also allow string message identifiers.

@craftytrickster
Copy link
Contributor

craftytrickster commented Oct 22, 2016

According to the spec, looks like you are right:

id
An identifier established by the Client that MUST contain a String, Number, or NULL value if included. If it is not included it is assumed to be a notification. The value SHOULD normally not be Null [1] and Numbers SHOULD NOT contain fractional parts [2]

Since the server has to send the exact same id back to the client, the server should be able to send a string back for a string id, and a number back for a number id.

@chergert
Copy link
Author

Agreed, I don't think mixing is an important feature. I think they should just be treated as opaque tokens.

@liamdawson
Copy link

Did #79 close this?

@nrc
Copy link
Member

nrc commented Oct 30, 2017

I'm pretty sure this is fixed now.

@nrc nrc closed this as completed Oct 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants