swagger-api / swagger-api/swagger-codegen
[Bug]: @EqualsAndHaschode without callsuper
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
When generating a child class with lombok annotations it generated @EqualsAndHaschode annotation but without callsuper=true, which leads to the following warning at build time:
warning: Generating equals/hashCode implementation but without a call to superclass, even though this class does not extend java.lang.Object. If this is intentional, add '@EqualsAndHashCode(callSuper=false)' to your type.
Swagger Codegen Version
3.0.75
Language / Generator
Java, SpringBoot
Expected Behavior
There should be an option to provide the value for callsuper and maybe a default value of true.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies the Java SpringBoot generator but names no file or test. Start by locating the generator templates and option handling for Lombok @EqualsAndHashCode, then inspect how generated child classes are covered by tests. Done means the callSuper value can be configured or given the agreed default, with generated code no longer producing the reported warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100