palantir / palantir/conjure-java-runtime-api
Split errors jar into client and server jars
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6
- Forks
- 33
- Avg merge
- 15h 50m
- Merged PRs (30d)
- 12
Description
https://github.com/palantir/conjure-java-runtime-api/blob/develop/errors/src/main/java/com/palantir/conjure/java/api/errors/RemoteException.java should be in it's own jar - it's only necessary to use when constructing errors from http BODYs. Defining errors, e.g. ErrorType and SerializableError, have nothing to do with http BODY interpretation.
This should help with versioning the client/server parts of error handling independently.
Contributor guide
No contributing guide indexed for this repository
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 with errors/src/main/java/com/palantir/conjure/java/api/errors/RemoteException.java and inspect how the errors module packages its classes. Separate HTTP BODY interpretation from ErrorType and SerializableError, then verify that the resulting client and server jars can be versioned independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100