-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Allow configuring the order of built-in EntityCallbacks #4914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Auditing and validation should be orthogonal aspects that ideally should not affect each other. We're using
I am not quite sure how this would really help as the value is a static one. I could imagine on the other side to introduce |
Hi @mp911de , I am not sure, If I could make clear the concerns regarding similar How do you know the order of entity callback if they all have the same order ? I think, there is already some kind of dependencies between callbacks. |
Isn't using Apart from that, introducing |
I will Provide a merge request |
Hi @mp911de , I noticed that this issue has been open for some time. |
Feel free to submit a pull request @yangchef1 |
…tyCallback. Added corresponding test cases for this functionality. Closes spring-projects#4914 Signed-off-by: yangchef1 <[email protected]>
…tyCallback. Added corresponding test cases for this functionality. Closes spring-projects#4914 Signed-off-by: yangchef1 <[email protected]>
…tyCallback. Added corresponding test cases for this functionality. Closes spring-projects#4914 Signed-off-by: yangchef1 <[email protected]>
Hi @mp911de ,
the
@Order
of the built-in EntityCallbacks (at the time of writingAuditingEntityCallback
andValidatingEntityCallback
) is not distinctive, both have the same configurationFurthermore, I would like to make the value referencable by exposing them as public constant, e.g.:
This change allows a clean code regarding ordering of the buit-in and app provided EntityCallbacks.
The text was updated successfully, but these errors were encountered: