Include inter-class relationship graph in schema documentation #2243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
|
eecavanna
changed the title
|
Closing because the upstream |
eecavanna
deleted the
2242-add-inter-class-diagram-generated-by-refscan-to-schema-documentation
branch
eecavanna
restored the
2242-add-inter-class-diagram-generated-by-refscan-to-schema-documentation
branch
|
Oops! This is the "upstream |
…fscan-to-schema-documentation
|
This is done—just holding off on merging until #2238 has been resolved. |
eecavanna
added
the
backlog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a "sequel" to #2241.
In this PR branch, I did two things:
make gendocto generate an inter-class diagram, storing it in the schema documentation website's file tree🕐 I do not expect this PR branch to be merged into
mainuntil issue #2238 has been resolved. I am ready for that merge to happen as soon as that issue has been resolved, though. In other words, I consider this branch to be "done."