You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2020. It is now read-only.
With a schema, many editors will provide type-ahead hints when editing JSON, for example, in VSCode. We should provide a JSON Schema for our Entity Type Descriptor. We should also publish this at a URL so that it can be referenced in config, such as in the example above.
Longer term, we should think about actually being JSON Schema, rather than kinda like JSON Schema.
The text was updated successfully, but these errors were encountered:
You realize that this request is for a descriptor for the es in a different version of JSON schema than es was actually based on? I was pretty surprised how different the new JSON schema is from what we used for entity services.
Also, the different between entity services and JSON schema is about supporting datatypes. I've not seen any JSON schema that supports datatypes reasonably.
So, laudable goal, but as you've assigned this to yourself, it looks like you recognize we need a little strategy as well as a task.
Take a look at https://hackolade.com/nosqldb.html#marklogic A visual JSON Schema editor build for NoSQL databases. Still need to do reverse-engineering of MarkLogic, but almost there...
With a schema, many editors will provide type-ahead hints when editing JSON, for example, in VSCode. We should provide a JSON Schema for our Entity Type Descriptor. We should also publish this at a URL so that it can be referenced in config, such as in the example above.
Longer term, we should think about actually being JSON Schema, rather than kinda like JSON Schema.
The text was updated successfully, but these errors were encountered: