-
-
Notifications
You must be signed in to change notification settings - Fork 184
normalization should not change KeyDataPair to NameValuePair #533
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
Conversation
rbri
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable for me, thanks for this.
Please add yourself as author to all changed files and maybe also to the pom (if you are not already in the list)
|
Jenkins will have a look at this.... |
|
sorry we are still at java8 :-) |
|
Yeah I've seen that but somehow eclipse didn't warn me when i used Java 11 features. |
| public KeyDataPair normalized() { | ||
| final KeyDataPair pair = new KeyDataPair( | ||
| this.getName(), | ||
| this.fileObject_ != null ? this.fileObject_ : new File(this.getValue()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new File(...) might do some normalization on the file name leading in the end to some new value -> Testcase?
maybe it is better to have a private constructor that allows to pass the values 1:1?
What do you think?
|
tests are looking good ! |
this should prevent manipulation of fields and make sure that "normalized" instances are identical copies if the source object is normalized already
|
@rbri please have a look at the additional commit. Perhaps that is what you had in mind ... |
|
i have nothing in mind ;-) and all the best for 2023 |
|
Thanks a lot and the all the best for you too. |
Fixes #532
See 39c58d2#r93713845