GO-JSONSCHEMA(1)

💖 NAME 💖

go-jsonschema — the lil bestie that generates Go code from JSON Schema files ✨ (yes, really, it just does that, and it does it so well)

🦋 DESCRIPTION 🦋

okay so picture this: you have JSON Schema files, right? and you need Go code. that's it. that's the whole vibe. go-jsonschema generates Go code from JSON Schema files, no cap, no drama, no manual struct-writing at 3am 💅

🚀 Usage:

go-jsonschema FILE ... [flags]

feed it one or more FILEs and it does its thing. iconic behaviour honestly 🫶

🎀 Flags:

okay bestie, here's the whole menu, every single one, don't skip any 🔥

• --capitalization strings — tell it how you want your Go capitalization to go for a given string. like, by default a field named 'id' becomes 'Id' (🙈 lowkey cursed), but with --capitalization ID it gets generated as 'ID'. glow-up achieved 💅
• --disable-custom-types-for-maps — do not generate custom types when generating maps. simple as that.
• --disable-omitempty — kills the addition of omitempty tag values. no omitempty for you 🚫
• --disable-omitzero — same energy, but for omitzero tag values. bye bestie 👋
• --disable-readonly-validation — do not include validation of readonly fields. hands off the readonly ones fr.
• -e, --extra-imports — allows extra imports (aka the non-standard-library ones) 🧚
• -h, --help — help for go-jsonschema. the classic. when in doubt, hit it up 💖
• --min-sized-ints — uses sized int and uint values based on the min and max values for the field. precision queen behavior 👑
• --minimal-names — uses the shortest possible names. no yapping, just names ✂️
• --only-models — generate only models — no unmarshal methods, no validation. just the models, nothing else, periodt.
• -o, --output string — the file to write to (- for standard output) (default "-"). so by default it's yapping straight at your stdout 🌸
• -p, --package string — the default name of the package to declare your Go files under, unless it gets overridden with --schema-package. the humble default 💜
• --resolve-extension strings — add a file extension that's used to resolve schema names. like, {"$ref": "./foo"} will also look for foo.json if you provide --resolve-extension json. it's giving detective energy 🔍
• --schema-output strings — the file to write (- for standard output) a specific schema ID to. must be in the format URI=FILENAME. respect the format bestie, it's not optional ✨
• --schema-package strings — the name of the package to declare Go files for a specific schema ID under. must be in the format URI=PACKAGE. again, format is the moment 🎀
• --schema-root-type strings — override the name used for the root type of a specific schema ID. must be in the format URI=TYPE. by default, it is derived from the file name. main character naming rights 👑
• -t, --struct-name-from-title — use the schema title as the generated struct name. let the schema name itself, slay 💅
• --tags strings — specify which struct tags to generate. defaults are json, yaml, mapstructure (default [json,yaml,mapstructure]) — the holy trinity fr fr 🫶
• -v, --verbose — verbose output. it will simply tell you everything 🗣️
• --yaml-extension strings — add a file extension that should be recognized as YAML. default is .yml, .yaml. (default [.yml,.yaml]) 🍓

ngl bestie, nothing in here is secretly dangerous, but if you're passing URI=FILENAME / URI=PACKAGE / URI=TYPE style values, the equal sign is load-bearing — get it wrong and it won't do the thing. iykyk 💀

and that's the whole page, no notes 💖 this was go-jsonschema version 0.24.1-1, dropped August 2026 — go forth and generate, you absolute icon, mwah 🎀✨🦋