logdna / logdna/env-config-node
Feature Request: Config.json option
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
It would be really nice if we could pass a fluent-schema instance to a `Config.json()` function to validate json configuration.
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 by locating the Config.json entry point in the repository and check how configuration is currently read and validated. Review how a fluent-schema instance could be accepted there, then add coverage for JSON configuration validation and confirm that valid and invalid configurations are handled as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100