openwisp / openwisp/netjsonconfig
JSON schema does not add default values to configuration dictionary
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 388
- Forks
- 87
- Avg merge
- 1h 26m
- Merged PRs (30d)
- 4
Description
Right now we have a lot of material specified in the schema for a backend but it is not used to fill the defaults for the user, so what is the benefit of having so much precise schema if it is not doing something for us?
Obviously this is a rant/question/"what would we like to do question", so please chime in and let's sort it out
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 identifies JSON schema handling and the configuration dictionary as the relevant areas, but names no files, tests, or entry points. First clarify with maintainers which schema defaults should be applied and when; done requires an agreed behavior and corresponding validation that configuration dictionaries receive those defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, python
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100