- Added Python 3.13 to supported Python version metadata.
- Fixed runtime
AttributeError
that occurred when creating a diagram that includes a model with a field that uses a type annotation with the ellipsis literal (e.g.,tuple[int, ...]
). (Issue #124, PR #127)
- Fixed handling of
typing.Annotated
in cases where it's not the outermost generic type. (Issue #122, PR #123)
- Fixed
StopIteration
error when rendering a model that has no fields. (Issue #120, PR #121)
- Fixed
AttributeError
when adding a model that has a field annotated with certain typing special forms likeAny
,Literal
, orTypeVar
instances. (Issue #114, PR #115)
- Fixed
ModuleNotFoundError
when importing fromerdantic.examples
without attrs installed.
- Fixed missing LICENSE file in sdist.
- Fixed outdated note in README.
Important
This release features significant changes to erdantic, primarily to the backend process of analyzing models and representing data. If you have been primarily using the CLI or the convenience functions create
, draw
, and to_dot
, then your code may continue to work without any changes. If you are doing something more advanced, you may need to update your code.
- Deprecated
--termini
option. Use the new--terminal-model
option instead. The shorthand option-t
remains the same. The--termini
option still works but will emit a deprecation warning.
- Deprecated
termini
argument forcreate
,draw
, andto_dot
functions. Use the newterminal_models
argument instead. Thetermini
argument still works but will emit a deprecation warning. - Added
graph_attr
,node_attr
, andedge_attr
arguments to thedraw
andto_dot
functions that allow you to override attributes on the generated pygraphviz object for the diagram.
A few changes have been made to the visual content of rendered diagrams.
- Changed the extraction of type names to use the typenames library. This should generally produce identical rendered outputs as before, with the following exception:
- Removed the special case behavior for rendering enum classes. Enums now just show the class name without inheritance information.
- Changed collection fields (e.g.,
List[TargetModel]
) to display as a "many" relationship (crow) instead of a "zero-or-many" relationship (odot + crow), treating the modality of the field as unspecified. A field will only be displayed as "zero-or-many" (odot + crow) if it is explicitly optional, likeOptional[List[TargetModel]]
. - Fixed incorrect representation of manyness for type annotations where the outermost annotation wasn't a collection type. (Issue #105)
- Added support for attrs classes, i.e., classes decorated by
attrs.define
. The source code for attrs support can be found in the new moduleerdantic.plugins.attrs
. - Added new example module
erdantic.examples.attrs
.
Significant changes have been made to the library backend to more strongly separate the model analysis process, the extracted data, and the diagram rendering process. We believe this more structured design facilitates customizing diagrams and simplifies the implementation for each data modeling framework. Please see the new documentation pages "Customizing diagrams" and "Extending or modifying erdantic" for details on the new design.
A summary of some key changes is below:
- Removed the adapter base classes
Model
andField
and the conrete adaptersDataClassModel
,DataClassField
,PydanticModel
, andPydanticField
.- Added new Pydantic models
ModelInfo
andFieldInfo
to replace the adapter system. These new models hold static data that have been extracted from models that erdantic analyzed.
- Added new Pydantic models
- Removed the adapter system and associated objects such as
model_adapter_registry
andregister_model_adapter
.- Added new plugin system to replace the adapter system as the way that modeling frameworks are supported. Plugins must implement two functions—a predicate function and a field extractor function—and be registered using
register_plugin
. All objects related to plugins can be found in the newerdantic.plugins
module and its submodules.
- Added new plugin system to replace the adapter system as the way that modeling frameworks are supported. Plugins must implement two functions—a predicate function and a field extractor function—and be registered using
- Renamed
erdantic.typing
module toerdantic.typing_utils
.
- Added PEP 561
py.typed
marker file to indicate that the package supports type checking. - Added IPython special method for pretty-print string representations of
EntityRelationshipDiagram
instances. - Removed support for Python 3.7. (PR #102)
This will be the last version that supports Python 3.7.
- Added version typer version ceiling of
< 0.10.0
due to incompatibility with a fix introduced in that version.
- Added support for Pydantic V1 legacy models. These are models created from the
pydantic.v1
namespace when Pydantic V2 is installed. (PR #94 from @ursereg)
- Added support for Pydantic V2.
- Removed support for Pydantic V1.
- Changed the init signature for
PydanticField
to work with Pydantic V2's API. - Added
is_many
andis_nullable
functions toerdantic.typing
.
- Changed Pydantic dependency to be
< 2
. This will be the final version of erdantic that supports Pydantic V1. - Changed to pyproject.toml-based build.
- Removed support for Python 3.6. (Issue #51, PR #56)
- Added support for modules as inputs to all entrypoints to diagram creation (
create
,draw
,to_dot
, CLI). For all modules passed, erdantic will find all supported data model classes in each module. (Issue #23, PR #58)- Added new parameter
limit_search_models_to
to all entrypoints to allow for limiting which data model classes will be yielded from searching a module.
- Added new parameter
- Fixed error when rendering a data model that has field using
typing.Literal
. (PR #49)
- Added support for showing field documentation from Pydantic models with descriptions set with
Field(description=...)
in SVG tooltips. This will add an "Attributes" section to the tooltip using Google-style docstring format and lists fields where thedescription
keyword argument is used. (Issue #8, PR #42)
- Fixed handling of forward references in field type declarations. Evaluated forward references will be properly identified. Forward references not converted to
typing.ForwardRef
will throw aStringForwardRefError
with instructions for how to resolve. Unevaluated forward references will throw anUnevaluatedForwardRefError
with instructions for how to resolve. See new documentation for more details. (Issue #40, PR #41) - Changed name of
erdantic.errors
module toerdantic.exceptions
. (PR #41) - Added new
ErdanticException
base class from which other exceptions raised within the erdantic library are subclassed from. Changed several existingValueError
exceptions to new exception classes that subclass bothErdanticException
andValueError
. (PR #41) - Changed
__lt__
method onModel
andEdge
to returnNotImplemented
instead of raising an exception to follow typical convention for unsupported input types. (PR #41)
- Fixed runtime error when rendering a data model that had a field containing
typing.Any
. (Issue #25, PR #26)
- Added option to specify models as terminal nodes. This allows you to truncate large diagrams and split them up into smaller ones. (PR #24)
- Fixed bug where Pydantic fields were missing generics in their type annotations. (PR #19)
- Added tests against static rendered DOT output. Change adapter tests to use parameterized fixtures. (PR #21)
- Fixed rendered example image in the package description on PyPI. (PR #18)
Initial release! 🎉