ts-json-schema-generator
ts-json-schema-generator copied to clipboard
vega
Generate JSON schema from your Typescript sources
📦 Published PR as canary version: 1.2.1--canary.1594.c05565b.0 :sparkles: Test out this PR locally via: ```bash npm install [email protected] # or yarn add [email protected] ```
This is a minimal reproduction of existing behavior around the `NodeParser` throwing an `UnknownNodeError` for valid in scope identifiers. eg. ``` // module.ts const y = "hello"; export const x...
A while ago I [submitted this](https://github.com/vega/ts-json-schema-generator/blob/898525113e9763f592664232a50824ca4da64d02/src/NodeParser/TypeReferenceNodeParser.ts#L32), but it certainly don't work for custom promises or classes that extends promises... A simple example of that is Prisma itself that uses a...
When [`stripInternal`](https://www.typescriptlang.org/tsconfig/stripInternal.html) is true in tsconfig and using `@internal` comments in jsdoc, its type declarations are omitted from the rest of the code. Is this feature implemented here? If not,...
Without `expose`, all types including type names from a single file are generated. When I add `expose: 'none'`, the type names are gone and are replaced with a single `'*'`...
Minimal reproduction here: https://github.com/vega/ts-json-schema-generator/pull/1560 Expected behavior: Cross module identifiers are able to have type inference. Actual behavior: Cross module identifiers result in `UnknownNode` error.
Consider the following type. ```typescript type Opt = { type: "typeA", reqProp: number } | { type: "typeB", optProp?: string } ``` ```json { "$ref": "#/definitions/Opt", "$schema": "http://json-schema.org/draft-07/schema#", "definitions": {...
```ts type A1 = { id_type: 'a1'; id: string; }; type A2 = { id_type: 'a2'; id: string; }; type C = { name: string; address: string; } type A1c...
Hello, Below is an example where interface could be ```ts export type ISchema = ({ foo: string } | { bar: string }) & { baz: string }; ``` Output...
Hi, Sorry for the dumb question but I'm struggling a bit to use this package. I'm exporting multiple Typescript interface, so I end up with a file like this: ```json...
