Conversation
…sociationModifierCoCo.java
…iationSymbolTableCompleter.java
… compilation errors
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.
Fix builder generation for abstract classes: Issue #119
Description:
This PR fixes an issue where the class-diagram generator creates a concrete build() method for abstract classes, preventing potential compiler errors.
Solution: Added an if check in BuilderDecorator.visit(ASTCDClass node) to check if a class is abstract, ensuring that the generation of the build() method is properly omitted or handled for abstract classes.
Testing: Added a test case in
BuilderDecoratorTestfeaturing an abstract class model to verify that builders for abstract classes are generated correctly without build() and that the build passes without errors.