-
Notifications
You must be signed in to change notification settings - Fork 2
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
New Map extension #67
Conversation
JanSchankin
commented
Jun 19, 2021
- Maps with primitve wrapper types as keys can now be persisted
+ BeanConverterExtensions use Types instead of Classes to be able to acces generic type parameters + PersistentBeanConverter is now sent to all BeanConverterExtensions for recursive conversions. Otherwise registered Extensions would be lost if an Extensions creates a new PersistentBeanConverter.
+ Fallback for unserializable special Collections
+Refactoring of the BeanConverterExtension as a result of the tests +Bugfixes
+Bugfixes
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.
I like the change of the API for the extensions, but we might want some simpler APIs for common use cases in the future, but thats another issue I guess.
}) | ||
.forEach(pair -> valueMap.put(pair[0], pair[1])); | ||
|
||
return (T) valueMap; |
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.
I think a conventional for each would be more readable, multi-line lambda + entryMap stream is too much in my opinion.
return new Object[]{key, value}; | ||
}) | ||
.forEach(pair -> convertedMap.put(pair[0], pair[1])); | ||
|
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.
same as below
…ary foreach instead of a Stream, since this leads to cleaner code.
Kudos, SonarCloud Quality Gate passed! |
I've created an issue for that (#69). |