Open
Conversation
Added support for custom constructors by checking if there are any operations with the same name as the class.
Adding support for custom constructors
WIP: modifying how I format the params when there is a custom class.
|
Great stuff, @JasonHertzog! I see one edge case though: When trying to make the default constructor private by adding a /**
*
*/
private MyObject() {
// TODO implement here
}
/**
* Default constructor
*/
public MyObject() {
}Maybe this could be addressed? |
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
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.
When a UML class has the same name as a UML operation it owns.
Example output:
` /**
* Default constructor
*/
public Person() {
}
Areas of future improvement: If it's a constructor, it could be good to also have documentation reflect that since right now it will only show the params in the docs.