-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separating class and its inherited class #43
Comments
I am also very interested in being able to represent inheritance and include Base/Child classes in the diagram, and also see what data fields are narrowed down (overridden) in child classes. @pjbull (you did the last commit so I mention you, sorry if you are not the maintainer) is this something that you see within the scope of erdantic? If so I might try to work on this (if I don't find a more suitable alternative that can do it) |
@apirogov Yeah, give it a shot and see where you get. I think the devil will be in the details in terms of providing users with options for how to show inheritance and when to not show it. (E.g., in our example we don't really want |
Chiming in to express my interest in this. |
As a user
I want to see the relation between a class and its inherited class and also separate the members where it should be
So that you will get a correct UML view of the classes.
example: https://github.com/drivendataorg/erdantic/blob/main/erdantic/examples/pydantic.py
Additional class:
(Although this is an erd package, it can have added value. I understand if this issue is closed as it might not fit the vision.)
The text was updated successfully, but these errors were encountered: