You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that I want the merged class to be called ISectionBlockMetadata
Describe the solution you'd like
I would like the ability to reverse which name is adopted for the merged class, for instance, in the above example I would I would expect the merged class to be
Describe alternatives you've considered
For my use case (typescript -> json schema -> pydantic), I've submitted a feature request to the typescript-json-schema library to add (if it doesn't already exist) the ability to transfer the name to the title within the json schema (details: YousefED/typescript-json-schema#554)
Additional context
N/A
The text was updated successfully, but these errors were encountered:
As an update, I have implemented a work around for typescript-json-schema, I think the ability to remove nested / duplicated structures will lessen the need for work on this tool.
on a different note, when I do --reuse-model it would be nice to have the option to merge the naming / reference into a single one. i.e. currently I might have something like
Is your feature request related to a problem? Please describe.
Currently, without --collapse-root-models, I get the following:
with --collapse-root-models, I get this:
The problem is that I want the merged class to be called ISectionBlockMetadata
Describe the solution you'd like
I would like the ability to reverse which name is adopted for the merged class, for instance, in the above example I would I would expect the merged class to be
Describe alternatives you've considered
For my use case (typescript -> json schema -> pydantic), I've submitted a feature request to the
typescript-json-schema
library to add (if it doesn't already exist) the ability to transfer the name to the title within the json schema (details: YousefED/typescript-json-schema#554)Additional context
N/A
The text was updated successfully, but these errors were encountered: