Allow customization of @RevisionTimestamp property name
#4003
+116
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spring-projects-issues
added
the
status: waiting-for-triage
…roperty name Signed-off-by: ChaedongIm <[email protected]>
mp911de
added
type: enhancement
mp911de
changed the title
@RevisionTimestamp property name
mp911de
pushed a commit
that referenced
this pull request
Sep 16, 2025
We now detect the property name annotated with RevisionTimestamp to determine the property name from the model instead of assuming a hard-coded timestamp property. Signed-off-by: ChaedongIm <[email protected]> See #2850 Original pull request: #4003
|
Thank you for your contribution. That's merged and polished now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue: #2850
Fixes #2850 by replacing hardcoded "timestamp" property name with dynamic @RevisionTimestamp field detection.