Replies: 4 comments 5 replies
-
This seems like a good idea. I would probably give precedence to annotation. For name maybe something like |
Beta Was this translation helpful? Give feedback.
-
One thing I don't like about this annotation approach is that you will end with dependency on some third-party library (in this case nrich) in your api module which contains request classes. Consequently, the request class is no longer clean. For example, for this reason, I avoid using Swagger annotations in request classes for API documentation. |
Beta Was this translation helpful? Give feedback.
-
I like this feature :). |
Beta Was this translation helpful? Give feedback.
-
We agreed to go with this. @SBolsec Can you please open the enhancement request? Any further discussion on this topic can be continued there. |
Beta Was this translation helpful? Give feedback.
-
Idea
Instead of having to define mappings between a form id and the corrresponding class through property files, an annotation could be added to the class which defines the form id.
Example
Current
Proposed
Open questions
Beta Was this translation helpful? Give feedback.
All reactions