-
Notifications
You must be signed in to change notification settings - Fork 148
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
[TASK] Use auto-generated hierarchy in class diagram #518
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a Composer script to run the tool, with the arguments you are using, including the tool as a dev
dependency? Currently, the rest of us are somewhat in the dark as to how you are generating this automatically.
I'm guessing that at present you don't have a solution for automatically updating the readme between the "start of" and "end of" comments, though that could ultimately be achieved. Assuming not, something that outputs an .md
(or whaterver) file to be inserted would suffice for now. If it outputs a fixed file (rather than to stdout
), then that filename would probably need to be added to .gitignore
.
This could be done as a separate PR first, using the command line that created the current content before this proposed change. Then updated in this PR to also generate the inheritance rules that are being moved to auto-generated with this PR.
Changes themselves seem fine, though I have a query about whether inheritence rules from in-built classes should be included. They weren't before (specifically: SourceException extends \Exception
).
Commentable <|.. Rule: realization | ||
SourceException <|-- OutputException: inheritance | ||
UnexpectedTokenException <|-- UnexpectedEOFException: inheritance | ||
Exception <|-- SourceException: inheritance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should inheritance from in-built classes be included?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I know, there is no option to configure this behavior. So if we want to automate this, I propose we stick to what the tool generates.
I have create #521 for the Composer script and would suggest moving this change here first to get it out of the way. |
…gram Now the only part of the class diagram which we need to maintain manually are the associations between classes.
cf13c18
to
bd81cd1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moving this change here first to get it out of the way.
Presume you mean merging this PR first? I'm happy with that.
I note the latest push is just a reordering and removal of the relationship with the built-in class.
Yes - I only rebased on top of the current |
Now the only part of the class diagram which we need to maintain manually are the associations between classes.