-
Notifications
You must be signed in to change notification settings - Fork 48
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
"Add missing parameters to ABAPDoc" rules for unit-test methods #103
Comments
Hi Suhas, just to be sure, the idea would be to add an option suppressing this rule in the context of FOR TESTING methods? (Or even FOR TESTING classes as a whole, so it wouldn't run on helper methods in those classes, either?) If this is not specific to test code versus product code, this option would help: Kind regards, |
Hi Jörg-Michael, I would rather skip the rule for aunit methods instead of providing an option. I don't think any one would like to document exceptions for aunit methods. methods SHOULD_NOT_ADD_ABAP_DOC for testing raising CX_STATIC_CHECK. In case some one wants to document these exceptions, (s)he can use the ADT quickfix (Ctrl+1) "Add missing parameters to documentation". KR, |
Hi Suhas, alright, this will be changed with the next release, meaning that no ABAP Doc line is added for exceptions of test methods. Nevertheless, if exceptions are already documented,
Instead of an option, I added some documentation … … so if someone comes up with convincing arguments why they need this, we could still add an option for it at a later point in time. Kind regards, |
Hi Suhas, thanks again for this issue – this is now included in version 1.5.4 which was just released! Kind regards, |
I have a minor gripe regarding the rule Add missing parameters to ABAPDoc in the context of aUnit methods.
Before running abapCleaner:
After running abapCleaner:
IMO, this rule should not be run in the context of aUnit methods. Maybe it is a case of personal taste 😉
The text was updated successfully, but these errors were encountered: