datalust / datalust/seq-logging
onRemoteConfigChange
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 33
- Forks
- 15
- Avg merge
- 5h 23m
- Merged PRs (30d)
- 6
Description
The following PR https://github.com/datalust/seq-logging/pull/64 has removed the functionality introduced by https://github.com/datalust/seq-logging/pull/23. Which potentially allows seq to control the logging level.
Was this intended?
Contributor guide
No contributing guide indexed for this repository
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 by comparing PR #64 with PR #23 to identify how onRemoteConfigChange and remote logging-level control changed. Check the issue's linked PRs and surrounding history to determine whether the removal was intentional. Done means documenting the decision and restoring or preserving the intended behavior, with tests covering the resulting configuration flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100