palantir / palantir/conjure-java
Enforce best practices
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 39
- Forks
- 49
- Avg merge
- 8h 22m
- Merged PRs (30d)
- 32
Description
What happened?
I have recently figured out that having an endpoint return a primitive value (even if it's behind an alias) is a really bad design choice, since it means the endpoint return value can never be extended. I suspect there might be a lot of these things that people have found, I was wondering if we could collect and enforce those learnings.
What did you want to happen?
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 does not identify any files, tests, or entry points. First clarify which best practices should be enforced and where endpoint return types are defined; done criteria are not yet specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100