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
Well, if it's used to create the setAdditionalProperties then is ok to have it, yet it would be better to add the setter using a custom rule like you mention.
Honestly, if the toString, equals and hashCode can be also generated to remove lombok completely, that would be nice.
Well, if it's used to create the setAdditionalProperties then is ok to have it, yet it would be better to add the setter using a custom rule like you mention.
Honestly, if the toString, equals and hashCode can be also generated to remove lombok completely, that would be nice.
I'm working on a replacement generator (#6080) to completely remove the Go-to-JSONSchema and the JSONSchema-to-Java code generation steps.
Once this is in place, it will be really easy to modify the templates so that the code is generated without Lombok annotations or anything else we want to change.
Describe the bug
Almost all the models are annotated with
@Setter
but the setters seem to be explicitly generated.Fabric8 Kubernetes Client version
SNAPSHOT
Steps to reproduce
kubernetes-client/kubernetes-model-generator/kubernetes-model-core/src/generated/java/io/fabric8/kubernetes/api/model/Pod.java
Line 36 in 409be3b
Expected behavior
The annotation should not be present when the setter is already generated:
kubernetes-client/kubernetes-model-generator/kubernetes-model-core/src/generated/java/io/fabric8/kubernetes/api/model/Pod.java
Line 106 in 409be3b
Runtime
other (please specify in additional context)
Kubernetes API Server version
1.25.3@latest
Environment
other (please specify in additional context)
Fabric8 Kubernetes Client Logs
No response
Additional context
This seems to be harmless and Lombok does not generate the setters if found one, but having one less annotation that does magical stuff is better.
The text was updated successfully, but these errors were encountered: