Question: what is the performance impact of implementing this in the typing system?

Hi @ThomasAribart, thanks for your awesome work, json-schema-to-ts looks very interesting!

I was wondering though, what performance impact can we expect implementing this in the typing system? A lot of TS logic needs to happen on the fly for inferring the schema TS types, and my worry is that when codebases grow, the TypeScript language server might take a long time to startup, and we’ll start feeling in in our editing experience. But maybe it’s all super fast and little work compared to all other things TS has to do on a codebase.

I imagine a few use cases where this matters:

• opening your editor, lang server starts, opening a file that uses a FromSchema type or two from other files
• opening your editor, lang server starts, opening a file with many/all schema’s in your app
• building your project with tsc

I’m now using a (more complex) build time solution, but if json-schema-to-ts has an insignificant perf impact it would make things easier and more elegant. Curious about your thoughts on this!

[ThomasAribart]

Sorry it took some time but I added a FAQ section with a paragraph on the subject !

Closing this issue !

[rattrayalex]

Full projects. There haven’t been isolated benchmarks on just schemas.