Open JooHyukKim opened 1 month ago
I like this idea. I think I'd like to get https://github.com/FasterXML/jackson-databind/pull/4396 merged before this, but we can proceed with renaming right after (technically it is not strictly necessary to order things this way but might be slightly less problem merging).
I like this idea. I think I'd like to get FasterXML/jackson-databind#4396 merged before this, but we can proceed with renaming right afte
Sounds good to me ✅
Proposal
I propose the following naming schema to provide a clear and consistent structure:
Serialization Side
PropertyWriter
remains the sameBeanPropertyWriter
remains the sameAnyGetterWriter
->AnyGetterPropertyWriter
Deserialization Side
SettableBeanProperty
->PropertyReader
ObjectIdValueProperty
->ObjectIdValuePropertyReader
CreatorProperty
->CreatorPropertyReader
SettableAnyProperty
->AnySetterPropertyReader
Example Class Hierarchy
Current (AS-IS)
PropertyWriter
->BeanPropertyWriter
->AnyGetterWriter
SettableBeanProperty
->ObjectIdValueProperty
/CreatorProperty
->SettableAnyProperty
Proposed (TO-BE)
PropertyWriter
->BeanPropertyWriter
->AnyGetterPropertyWriter
PropertyReader
->ObjectIdValuePropertyReader
/CreatorPropertyReader
->AnySetterPropertyReader
Benefits
Note
We will talk along the way the classes that are not mentioned here, yet.