You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the input to BeanConverter#getPropertyList is a Map, it should use only the map's keys as the names of the properties for the target object. Exclusions should still apply, however.
The text was updated successfully, but these errors were encountered:
* Rename protected getPropertyList to getPropertySet (since it returns
a Set<String> and saying we return a List is just a bit confusing...)
* Change BeanConverter#getPropertySet so that, when the input is a
Map, we assume the properties are simply the keys in the Map
Fixes#403
sleberknight
changed the title
BeanConverter should take Map properties as the property list
BeanConverter#convert should use Map keys as the property names
Nov 4, 2020
* Better Map input handling in BeanConverter#convert
* Rename protected getPropertyList to getPropertySet (since it returns
a Set<String> and saying we return a List is just a bit confusing...)
* Change BeanConverter#getPropertySet so that, when the input is a
Map, we assume the properties are simply the keys in the Map
Fixes#403
* * Rename exclusionList property (which is a Set) to just exclusions
When the input to
BeanConverter#getPropertyList
is aMap
, it should use only the map's keys as the names of the properties for the target object. Exclusions should still apply, however.The text was updated successfully, but these errors were encountered: