ts-json-schema-generator
ts-json-schema-generator copied to clipboard
Generate JSON schema from your Typescript sources
### How to produce `ts-json-schema-generator -f './tsconfig.json' -p './type/' -o './scheme.json' ./type/a.ts ``` export type TypeNameOne = { prop1: number } ``` ./type/b.ts ``` export type TypeNameOne = { prop2:...
### How to produce `ts-json-schema-generator -f './tsconfig.json' -p './type.ts' -o './scheme.json' --id='api'` ./type.ts ``` export type ApiSchema = { N: B } export type B = string ``` ### What...
Very similar (hence I copied the description and just substituted inputs and outputs) issue to https://github.com/vega/ts-json-schema-generator/issues/1682, but now caused by using an exported type as a discriminator. For example, ```...
resolves https://github.com/vega/ts-json-schema-generator/issues/1619 Allows for a single `@example` in comment tags. Previously the parser assumes that there might be multiple such tag in comments and add it to an array of...
In short, I want pic below:  But can only have pic below:  https://github.com/vega/ts-json-schema-generator/blob/fad197f4f32d070a9fb0e8228cbb98ee70d9f83c/src/AnnotationsReader/ExtendedAnnotationsReader.ts#L91-L94 Code above reads in the `@example` jsdoc field and...
I have a simple User interface and try to create the schema. The User can have some functions, which won't work so there is a Jsonify type that will strip...
Hello, In my `tsconfig.json` I have `target: esnext` and `module: esnext`, `moduleResolution: node` etc, regardless, I am getting errors such as these: ``` error TS18028: Private identifiers are only available...
Bumps [glob](https://github.com/isaacs/node-glob) from 8.1.0 to 9.2.1. Changelog Sourced from glob's changelog. cganhe glo 9.2 Support using a custom fs object, which is passed to PathScurry add maxDepth option add stat...
Hello! I'm currently trying to implement `ts-json-schema-generator` on [a TypeScript project](https://github.com/Stilic/server/blob/openapi/scripts/schema.js). I came accros an issue where inline imports can't be parsed like normal imports (they are considered as unknown...
`node_modules/ts-json-schema-generator/dist/src/NodeParser/TypeReferenceNodeParser.js:52 return this.childNodeParser.createType(typeSymbol.declarations.filter((n) => !invalidTypes[n.kind])[0], this.createSubContext(node, context));` types: ` /** * 自定义组件路由对象 * @description 可获得当前自定义组件的路由对象,路由方法与全局路由方法功能相同,唯一区别在于调用时,相对路径是相对于该自定义组件 * @version 2.7.22 */ readonly router: Shared.IRouter; `