Parsing all types in a file with *
See original GitHub issueCurrently I use the following command to generate a schema:
ts-json-schema-generator --path test.ts --type MyInterface
However, instead of just generating a schema containing MyInterface
, is it possible to collect all types within test.ts
and write them in to the same schema?
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Parse information and data from files with Python, Java, Ruby ...
Let's take a deep dive into parsing different data types using various tools and techniques (especially with OCR).
Read more >Build an interface to parse text from any type of document
Build an interface to parse text from any type of document. Extract text from txt, docx, pdf, html, pptx files, and more, using...
Read more >Best approach to parse text files that contain multiple types of ...
I need to parse some text files that have different types of delimiters (tildes, spaces, commas, pipes, caret characters).
Read more >c# - How should I separate File Parse Classes?
I have three different classes. Generally I am creating a file parser. The classes: CustomerData - which shows text Data Model. A File...
Read more >Parsing text files with the TextFieldParser object - Visual Basic
The TextFieldParser object allows you to parse and process very large file that are structured as delimited-width columns of text, such as log ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Part of https://github.com/vega/ts-json-schema-generator/issues/104
Ok, here’s the PR: https://github.com/vega/ts-json-schema-generator/pull/135
I intentionally did not do that because
name?
in a parameter list means that the parameter is optional. Sincename
is not the last parameter, this would not work. Sostring | undefined
is more consistent. Feel free to adapt if you’d rather seetype?: string;
inConfig
.Finally, also feel free to revert commit https://github.com/vega/ts-json-schema-generator/commit/a4ce8ccd731b0fa51faef031e41ef8905d0a101a if you think this is going into the wrong direction. I’d be happy to start over.