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
If no explicit naming is present via annotation, implicit naming can be used. This should not be a compile warning (some devs are happy for property names to be part of the contract of the class). Perhaps it can be noted in the generated javadoc?.
Add implicit naming code to BuilderModelProducer for factory-methods which do have properties but do NOT have @FactoryProperties
Add JavaDoc to StringTemplate templates regarding implicit naming
Add JavaDoc to StringTemplate templates @linking to source method/constructor which is used by the builder
Add tests for implicit naming
Update documentation regarding implicit naming
The text was updated successfully, but these errors were encountered:
I am not sure if I see the purpose of implicit property names for factory-method parameters (respectively constructor parameters).
At least, if we don't use something like paranamer in PB.
If the parameter names are already correct, why does the user need to list them out again (i.e. as per @ConstructorProperties, explicit name mappings are optional). PB should already have full view of these names as it operates on the source so Paranamer isn't required I think.
You are right.
The parameter names are accessible during compile time for the annotation processor. I didn't realize that.
So I think we should do this!
If no explicit naming is present via annotation, implicit naming can be used. This should not be a compile warning (some devs are happy for property names to be part of the contract of the class). Perhaps it can be noted in the generated javadoc?.
The text was updated successfully, but these errors were encountered: