nalukit / malio Goto Github PK

self-declaration ... :-)

Having a class marked as MalioValidator and use this class as an array type causes an compilation error.

Create a test to check if the value of an variable is an UUID.

Create a new check for numbers and there unboxed types to check that the value is not zero. It should also check, that the value is greater zero.

add a boolean value to the annotation to allow negative values

ATM the error messages are generated by the framework. There is no chance to change it by the user.

Add a optional message parameter to each variable annotation. It the message parameter is set, use the value from the parameter - otherwise use the default value ...

Instead of logging 'Malio-Processor' it logs 'Nalu-Plugin-GWT-Processor`

Currently, the @Size annotation can only be used for variables of type Collection.
It would be useful if this annotation could also be applied to arrays.

For example like so:

@MalioValidator
public class DepartmentManager {

  @Size(min = 1, max = 50)
  private int[] subordinateEmployeeIds;

}

PS: Good work so far 👍

The class documentations of @NotEmpty and @NotBlank currently contain a small mistake. In both class is described:
The annotation indicates that the String should be empty - if the value is not null.

See:

The correct description should be something like: The annotation indicates that the String should **not** be empty - if the value is not null.

The number of generated classes is really high. One for the validator and one for each variable and variable annotation of malio.

Instead of generating classes for each variable and annotation generate a method inside the validator.

Currently, Malio always generates a check- and a validate-method. In some cases, you might only use one of both. In this case Malio will generate a lot of useless code.

To avoid it, make the generation configurable.

Add two parameters to the `MalioValidator-annotation:

• generateCheckMethod: to trigger the generation of the check-method. (default: true)
• generateValidateMethod: to trigger the generation of the validate-method. (default: true)

which control the generation of both methods.