UNPKG

ts-json-schema-generator

Version:

Generate JSON schema from your Typescript sources

95 lines (69 loc) 3.69 kB
# ts-json-schema-generator [![CircleCI](https://circleci.com/gh/vega/ts-json-schema-generator.svg?style=svg)](https://circleci.com/gh/vega/ts-json-schema-generator) [![codecov](https://codecov.io/gh/vega/ts-json-schema-generator/branch/master/graph/badge.svg)](https://codecov.io/gh/vega/ts-json-schema-generator) [![npm dependencies](https://david-dm.org/vega/ts-json-schema-generator.svg)](https://www.npmjs.com/package/ts-json-schema-generator) [![npm version](https://img.shields.io/npm/v/ts-json-schema-generator.svg)](https://www.npmjs.com/package/ts-json-schema-generator) [![Greenkeeper badge](https://badges.greenkeeper.io/vega/ts-json-schema-generator.svg)](https://greenkeeper.io/) Extended version of [https://github.com/xiag-ag/typescript-to-json-schema](https://github.com/xiag-ag/typescript-to-json-schema). Inspired by [`YousefED/typescript-json-schema`](https://github.com/YousefED/typescript-json-schema). Here's the differences list: * this implementation does not use `typeChecker.getTypeAtLocation()` (so probably it keeps correct type aliases) * processing AST and formatting JSON schema have been split into two independent steps * not exported types, interfaces, enums are not exposed in the `definitions` section in the JSON schema ## Contributors This project is made possible by a [community of contributors](https://github.com/vega/ts-json-schema-generator/graphs/contributors). We welcome contributions of any kind (issues, code, documentation, examples, tests,...). Please read our [code of conduct](https://github.com/vega/vega/blob/master/CODE_OF_CONDUCT.md). ## Usage ```bash npm install --save ts-json-schema-generator ./node_modules/.bin/ts-json-schema-generator --path 'my/project/**.*.ts' --type 'My.Type.Full.Name' ``` ## Options ``` -t, --type 'My.Type.Full.Name' The type the generated schema will represent. If omitted, the generated schema will contain all types found in the files matching path. The same is true if '*' is specified. -e, --expose <all|none|export> all: Create shared $ref definitions for all types. none: Do not create shared $ref definitions. export (default): Create shared $ref definitions only for exported types. -f, --tsconfig 'my/project/tsconfig.json' Use a custom tsconfig file for processing typescript (see https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) instead of the default: { "compilerOptions": { "noEmit": true, "emitDecoratorMetadata": true, "experimentalDecorators": true, "target": "ES5", "module": "CommonJS", "strictNullChecks": false, } } -r, --no-top-ref Do not create a top-level $ref definition. -j, --jsDoc <extended|none|basic> none: Do not use JsDoc annotations. basic: Read JsDoc annotations to provide schema properties. extended (default): Also read @nullable, and @asType annotations. -u, --unstable Do not sort properties. -s, --strict-tuples Do not allow additional items on tuples. -c, --skip-type-check Skip type checks for better performance. -k, --validationKeywords Provide additional validation keywords to include. ``` ## Current state * `interface` types * `enum` types * `union`, `tuple`, `type[]` types * `string`, `boolean`, `number` types * `"value"`, `123`, `true`, `false`, `null`, `undefined` literals * type aliases * generics * `typeof` * `keyof` * conditional types ## Debug `npm run debug -- --path 'test/valid-data/type-mapped-array/*.ts' --type 'MyObject'` And connect via the debugger protocol. [AST Explorer](https://astexplorer.net/) is amazing for developers of this tool!