Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Description
As discussed in the senate, we often have to mark parameteriztion methods as unused to avoid our IDEs warning of methods not being used. However, a method being unused doesn't make it very clear to the reader why it is used and why it shouldn't be deleted. We could try to create a custom annotation to mark these methods instead to make it clearer to the reader. Functionally, it would work the same as the suppression, but it could be labelled as something like @TestParameters
Hint:
This is not a big problem, but might be fun as slacktime, for example
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- mentioned in
-
Page Loading...