palantir / palantir/conjure-java
Support strict staged builders on collections/optionals
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 39
- Forks
- 49
- Avg merge
- 8h 22m
- Merged PRs (30d)
- 32
Description
What happened?
Omitting optional fields reduces boilerplate, but also makes it easier to accidentally forget to plumb through a new field across different parts of an application.
What did you want to happen?
Either a flag or a separate builder which generates stages for required & optional fields (& forces passing in explicitly empty collections/optionals)
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 names no files, tests, or entry points. Start by locating the builder-generation code and existing collection/optional handling, then compare generated APIs; done means an agreed flag or separate staged builder that requires explicit empty values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100