Add diagram of the Transform class hierarchy#117
Open
Beetelbrox wants to merge 1 commit intoCBDD:mainfrom
Open
Add diagram of the Transform class hierarchy#117Beetelbrox wants to merge 1 commit intoCBDD:mainfrom
Beetelbrox wants to merge 1 commit intoCBDD:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As an attempt to better understand how the code is structured I generated a Mermaid diagram of the Tranform class hierarchy and thought that it could be useful to have it in the repo as dev docs.
If useful we can enrich this graphs while we figure out how to reorganize the situation, also might be a nice bookkeeping for how the code structure changed over time.