The JSON representation of the Range type is an object form, theres no built in (de)serializer for the json representation of range. This issue is prominent with the Json type and the HTTP Client.
Solution
There should be a json contract resolver specifically for edgedb formatted json that the user and library has direct access to. This allows for any future types with their own json format to be easily added to the serialize/deserialize step of the json and http client.
Summary
The JSON representation of the Range type is an object form, theres no built in (de)serializer for the json representation of range. This issue is prominent with the Json type and the HTTP Client.
Solution
There should be a json contract resolver specifically for edgedb formatted json that the user and library has direct access to. This allows for any future types with their own json format to be easily added to the serialize/deserialize step of the json and http client.