v2.0.0

What's Changed

• v2 by @phillipdupuis in #49
• Support for both Pydantic V1 and V2 by @khalo-sa in #38

New Contributors

• @khalo-sa made their first contribution in #38

Full Changelog: v1.0.10...v2.0.0

v1.0.10

What's Changed

• Creating a github action for pydantic-to-typescript by @phillipdupuis in #23
• Check whether json2ts exited without any errors before processing the generated ts file by @qwyt in #14
• The --json2ts-cmd option should not be validated via 'shutil.which' by @phillipdupuis in #26

New Contributors

• @qwyt made their first contribution in #14

Full Changelog: v1.0.9...v1.0.10

v1.0.9

What's Changed

• Added tests for exception raising
• Removed click dependency, since the built-in argparse module is sufficient
• Added basic action to github marketplace

Exclude models by name + bugfixes

Primary changes:

• added the option to exclude pydantic models from the generated typescript definitions. This is done by providing the names of the models which should be excluded. For CLI users, this can be accomplished via the --exclude option, ex: --exclude MyCustomBaseModel to exclude the model named MyCustomBaseModel from the results. And if you want to exclude multiple models, provide multiple options, ex: --exclude Foo --exclude Bar to exclude both Foo and Bar. For python users, this same behavior can be accomplished by passing a tuple of model names as the exclude kwarg to generate_typescript_defs.

Additional changes:

• fixed tests (even though they aren't part of CI currently) to reflect the new comment format, including the eslint-disable directive.
• fixed a bug in which pydantic2ts forced python progams to start logging at the DEBUG level. Logging at the DEBUG level will now only occur if pydantic2ts is invoked via the CLI. If it is called from within another python program, it will use whatever logging configuration has already been set up.

1.0.6

Bugfixes, black formatting, updated the --module argument to accept a…