schematyper
schematyper copied to clipboard
Generates Go types based on JSON Schemas
input ` { "description": "JSON schema for CSL input data", "$schema": "http://json-schema.org/draft-03/schema#", "id": "https://github.com/citation-style-language/schema/raw/master/csl-data.json", "type": "object", "properties": { "family": { "type": "string" }, "given": { "type": "string" }, "dropping-particle": {...
panics with the following message `2020/03/21 13:07:39 Can't resolve: (#/items/properties/collection-editor/items #/items/properties/reviewed-author/items #/items/properties/original-author/items #/items/properties/director/items #/items/properties/interviewer/items # #/items/properties/container-author/items #/items/properties/editor/items #/items/properties/composer/items #/items)` when running against this file https://raw.githubusercontent.com/citation-style-language/schema/master/csl-data.json
Embedded structs are generated without any explicit json tag, leaving the interpretation of the embedded struct ambiguous. Adding the `inline` option to the embedded struct's json tag.
based on the following JSONSchema I would like to propose the generation of a New() function. ```json { "definitions": {}, "$schema": "http://json-schema.org/draft-07/schema#", "$id": "http://example.com/root.json", "type": "object", "title": "The Root Schema",...
Right now using `allOf` results in embedding any `$ref`s and creating new structs for those that are defined in a new block. For those not using `$ref` would it be...
It would be good to support allowing specifying struct tags in some way. JSON schema doesn't have a concept which maps nicely to it, but maybe something like `additionalProperties` or...
In some cases I can get json with multiple schemas for example REST definition GET/POST/DELETE etc. This change will try to find node in json and use it as schema.
input example: ```json { "$schema": "http://json-schema.org/draft-04/schema", "type": "object", "properties": { "name": { "type": "string" }, "name$": { "type": "string" }, "name-": { "type": "string" }, "schema": { "type": "string" },...
Fix build with current Go.