Allow @Consumes and @Produces on packages
- Dominant language
- Java
- Stars
- 400
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
Versioning API is hard, and there's no real good choices. But if the API designers go for vendoring in the mimetype (like `application/api.v1+json`, `application/api.v2+json`, etc...)
It could be nice to annotate the package or a parent package. But currently this is not possible because the annotations are limited to classes and methods (of course implementation have to be aware of the package annotation in some way, hibernate do).
The application developers could apply filters globally depending on the content-type, e.g. exception mappers, custom objectmappers, etc...
Contributor guide
Research direction
Start by reviewing the @Consumes and @Produces annotation definitions and the package-level behavior described in the issue. Determine how package annotations should be recognized at runtime, then verify that package-level media types can affect global content-type handling such as exception mappers and custom object mappers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100