eclipse-ee4j / eclipse-ee4j/jersey
Integration: Do not require all properties
Open
Nobody has claimed this yet.
performance
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
Pull request for a property is performance-wise better than asking for all properties.
Config sources backed properties are time-consuming to pass to a map of properties.
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 integration code that handles config sources and maps their properties; done should mean callers can request only needed properties instead of requiring all properties, with performance coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100