ConfigHubPub / ConfigHubPub/ConfigHubPlatform
Client API lacks access to any sort of partial context resolution
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
The workflow I have going on for a project uses 2 out of the 3 context levels purely for administrative organization, but the program itself only really cares about the most narrow context level for what it retrieves. I notice that in the code base for the RepositoryPropertiesResolver that the method for resolving the client's context only respects full context, where as there also exists a method that will resolve a partial context. Are there any plans to give the client the option to resolve partial contexts in the future?
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
Start with core/src/main/java/com/confighub/core/resolver/RepositoryPropertiesResolver.java and compare the client context-resolution method with the existing partial-context resolution method. Determine the API shape needed to expose partial resolution and confirm that clients can select it without changing full-context behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100