Improve response for create calls
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by tracing how create calls handle the 201 response and Location header when followLocation is omitted, then compare that path with the automatic Get path. The work is done when the non-following path returns an empty resource containing the created resource ID, while the existing followLocation behavior remains intact.
Written by the indexing model from the issue text.
Description
Create calls in Kill Bill typically return 201 with a Location header. When followLocation is specified, there is Get to automatically fetch the resource; however, when followLocation is not specified, there no response returned and no easy way to even get the ID of the resource.
We would like to at least return an empty resource with the ID to make it easy for the caller.
- Dominant language
- Java
- Stars
- 35
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from killbill/killbill-client-java
-
Migrate away from Joda-Time to java.timeMay be free again @sbrossie claimed this 269 days ago, and no pull request is open. Openenhancement
killbill/killbill-client-java#144 · 1 comment · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
killbill/killbill-client-java#140 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
killbill/killbill-client-java#136 · 7 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
killbill/killbill-client-java#135 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
killbill/killbill-client-java#131 · 1 comment ·
All issues in killbill/killbill-client-java
Similar issues
-
component/data-layer
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
RegistryExceptionHandler uses self-referencing basePackageClasses instead of a controller classOpenbug finsim-registry good-first-issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
? - Needs Triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
NVIDIA/cudf-spark#17063 ·
Maintainers usually reply within 2 days
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100