No longer wrapping complex types in an auxiliary JSON object #2599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Complex types were wrapped in an auxiliary object to avoid ambiguities between the JSON representation of containers and "lists as a sole argument" on the JSON-RPC level. This is not necessary, as complex types are not automatically deserializable through this path anyway. This PR removes wrapping around complex types, leaving rationals as the only values that are wrapped when encoding values as JSON objects.
FIxes usethesource/rascal-language-servers#944