You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a getter that accompanies an attribute setter is used for type checking. The return type of the getter is compared with the argument type of the setter. This check becomes irrelevant because getters may be hidden. Getters that are done with Lombok @Getter will not be visible when the de-lombok step is out of the F!F build.
Attributes of an enum type will always have the enum as argument type. The check for getXxxEnum() to find the enum type will become irrelevant and can be removed.
A lot of information is lost if we don't delombok our code, because the Javadoc tool does not use the lombok plugin to do annotation processing. The XSD diff which I tested only on the core module code had about 500 lines of differences. The current solution is in the PR, keeping the delombok step.
If number 2 (enum attributes) does not make sense anymore, feel free to do that activity. Please compare the output XSD on the master, to see if no (real) differences are there.
Two tasks of this method can be removed:
See frankframework/frankframework#6344.
The text was updated successfully, but these errors were encountered: