Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/omissis/go-jsonschema
A tool to generate Go data types from JSON Schema definitions.
https://github.com/omissis/go-jsonschema
code-generation codegenerator go golang json json-schema
Last synced: 7 days ago
JSON representation
A tool to generate Go data types from JSON Schema definitions.
- Host: GitHub
- URL: https://github.com/omissis/go-jsonschema
- Owner: omissis
- License: mit
- Created: 2018-09-27T17:36:32.000Z (about 6 years ago)
- Default Branch: main
- Last Pushed: 2024-12-02T06:08:55.000Z (11 days ago)
- Last Synced: 2024-12-02T07:23:16.335Z (11 days ago)
- Topics: code-generation, codegenerator, go, golang, json, json-schema
- Language: Go
- Homepage:
- Size: 615 KB
- Stars: 594
- Watchers: 13
- Forks: 95
- Open Issues: 42
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-golang-repositories - go-jsonschema
README
**go-jsonschema is a tool to generate Go data types from [JSON Schema](http://json-schema.org/) definitions.**
This tool generates Go data types and structs that corresponds to definitions in the schema,
along with unmarshalling code that validates the input JSON according to the schema's validation rules.
## Badges
[](https://github.com/omissis/go-jsonschema/releases/latest)
[](https://github.com/omissis/go-jsonschema/actions?workflow=development)
[](/LICENSE.md)
[](https://tip.golang.org/doc/go1.22)
[](https://github.com/omissis/go-jsonschema)
[](https://github.com/omissis/go-jsonschema)
[](https://github.com/omissis/go-jsonschema)
[](https://github.com/omissis/go-jsonschema/commits)
[](https://conventionalcommits.org)
[](https://codecov.io/gh/omissis/go-jsonschema)
[](https://codeclimate.com/github/omissis/go-jsonschema)
[](https://goreportcard.com/report/github.com/omissis/go-jsonschema)
## Installing
* **Download**: Get a release [here](https://github.com/atombender/go-jsonschema/releases).
* **Install from source**: To install with Go 1.22+:
```shell
go get github.com/atombender/go-jsonschema/...
go install github.com/atombender/go-jsonschema@latest
```
* **Install with Brew**: To install with [Homebrew](https://brew.sh):
```shell
brew tap omissis/go-jsonschema
brew install go-jsonschema
```
## Contributing
This project makes use of [go workspaces](https://go.dev/ref/mod#workspaces) in order to ease testing of the
generated code during development while keeping the codebase as tidy and maintainable as possible.
It's an unusual choice, but it allows to not only test the code-generation logic, but also the generated code itself.
## Usage
At its most basic:
```shell
go-jsonschema -p main schema.json
```
This will write a Go source file to standard output, declared under the package `main`.
You can generate code for multiple schemas in one run, optionally writing to different files inside different packages:
```shell
$ go-jsonschema \
--schema-package=https://example.com/schema1=github.com/myuser/myproject \
--schema-output=https://example.com/schema1=schema1.go \
--schema-package=https://example.com/schema2=github.com/myuser/myproject/stuff \
--schema-output=https://example.com/schema2=stuff/schema2.go \
schema1.json schema2.json
```
This will create `schema1.go` (declared as `package myproject`) and `stuff/schema2.go` (declared as `package stuff`).
If `schema1.json` refers to `schema2.json` or viceversa, the two Go files will import the other depended-on package.
Note the flag format:
```text
--schema-package=https://example.com/schema1=github.com/myuser/myproject \
^ ^
| |
schema $id full import URL
```
### Special types
In a few cases, special types are used to help with serializing/deserializing
data frrom JSON. Namely a custom types is provided for the following semantic
types:
* `SerializableDate`
* `SerializableTime`
These types are needed because there is no native type provided by Go which
properly handles them.
## Status
While not finished, go-jsonschema can be used today. Aside from some minor features,
only specific validations remain to be fully implemented.
### Validation
* Core ([RFC draft](http://json-schema.org/latest/json-schema-core.html))
* [x] Data model (§4.2.1)
* [x] `null`
* [x] `boolean`
* [x] `object`
* [x] `array`
* [x] `number`
* [ ] Option to use `json.Number`
* [x] `string`
* [ ] Location identifiers (§8.2.3)
* [x] References against top-level names: `#/$defs/someName`
* [ ] References against nested names: `#/$defs/someName/$defs/someOtherName`
* [x] References against top-level names in external files: `myschema.json#/$defs/someName`
* [ ] References against nested names: `myschema.json#/$defs/someName/$defs/someOtherName`
* [x] Comments (§9)
* Validation ([RFC draft](http://json-schema.org/latest/json-schema-validation.html))
* [ ] Schema annotations (§10)
* [x] `description`
* [x] `default` (only for struct fields)
* [ ] `readOnly`
* [ ] `writeOnly`
* [ ] ~~`title`~~ (N/A)
* [ ] ~~`examples`~~ (N/A)
* [ ] General validation (§6.1)
* [x] `enum`
* [x] `type` (single)
* [x] `type` (multiple; **note**: partial support, limited validation)
* [ ] `const`
* [X] Numeric validation (§6.2)
* [X] `multipleOf`
* [X] `maximum`
* [X] `exclusiveMaximum`
* [X] `minimum`
* [X] `exclusiveMinimum`
* [X] String validation (§6.3)
* [X] `maxLength`
* [X] `minLength`
* [X] `pattern`
* [ ] Array validation (§6.4)
* [X] `items`
* [x] `maxItems`
* [x] `minItems`
* [ ] `uniqueItems`
* [ ] `additionalItems`
* [ ] `contains`
* [ ] Object validation (§6.5)
* [x] `required`
* [x] `properties`
* [ ] `patternProperties`
* [ ] `dependencies`
* [ ] `propertyNames`
* [ ] `maxProperties`
* [ ] `minProperties`
* [ ] Conditional subschemas (§6.6)
* [ ] `if`
* [ ] `then`
* [ ] `else`
* [ ] Boolean subschemas (§6.7)
* [ ] `allOf`
* [ ] `anyOf`
* [ ] `oneOf`
* [ ] `not`
* [ ] Semantic formats (§7.3)
* [x] Dates and times
* [ ] Email addresses
* [ ] Hostnames
* [ ] IP addresses
* [ ] Resource identifiers
* [ ] URI-template
* [ ] JSON pointers
* [ ] Regex
## License
MIT license. See `LICENSE` file.