ConfigHubPub / ConfigHubPub/ConfigHubPlatform
Pub Sub Mechanism
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
In order to more effectively reduce load and regular polling, I'd like to propose a new feature of publishing out changes when they occur. The notification can be siloed off by Repository and include enough information to keep a valid cache without constant polling.
For Additions:
- qualified context
- Files affected
- Values of Key
For Modifications:
- qualified context (Before and after)
- Files affected
- Values of Key (Before and after)
For Deletions:
- qualified context deleted
- Files affected
- Deleted value of keys
Context value Additions:
- context key effected
- value of new key
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 how repository changes are recorded and exposed, then determine where publication would belong and what consumers must receive for additions, modifications, and deletions. Done should include an agreed design and a working per-repository notification mechanism that supports cache updates without constant polling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100