palantir / palantir/conjure-java
suppress or fix warnings in generated code
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 39
- Forks
- 49
- Avg merge
- 8h 22m
- Merged PRs (30d)
- 32
Description
What happened?
There are warnings in eclipse on generated code.
I tried to suppress them in https://github.com/palantir/gradle-conjure/pull/951 but if we can suppress them at the source, that would be great.
All methods in a class DefaultBuilder implements Builder seem to be missing @Override
These can be unused:
_plainSerDe on Async and Blocking classes.
UndertowRuntime runtime on an Endpoint.
There may be more, but I am currently working on a very small project with only these warnings.
What did you want to happen?
No warnings in eclipse on generated code.
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
Start by inspecting the generated DefaultBuilder, Async and Blocking classes, and Endpoint output described in the issue; the attempted suppression is discussed in gradle-conjure PR 951. Reproduce the Eclipse warnings on a small generated project and trace them back to the generator. Done means generated code produces no Eclipse warnings, including missing @Override and unused fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100