Don't make CommandDescription final as to allow mocks
- Construction of a CommandDescription requires a lot of fields to be set. In most tests we only care about one or two fields -> having to set a lot of fields to dummy values is not very nice.
This commit is contained in:
parent
8aa573b9ed
commit
6db778387d
@ -19,7 +19,8 @@ import static java.util.Arrays.asList;
|
|||||||
* {@code /authme} has a child whose label is {@code "register"}, then {@code /authme register} is the command that
|
* {@code /authme} has a child whose label is {@code "register"}, then {@code /authme register} is the command that
|
||||||
* the child defines.
|
* the child defines.
|
||||||
*/
|
*/
|
||||||
public final class CommandDescription {
|
@SuppressWarnings("checkstyle:FinalClass") // Justification: class is mocked in multiple tests
|
||||||
|
public class CommandDescription {
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* Defines the labels to execute the command. For example, if labels are "register" and "r" and the parent is
|
* Defines the labels to execute the command. For example, if labels are "register" and "r" and the parent is
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user