Bug: missing config.yml validations
- Dominant language
- JavaScript
- Stars
- 19.4k
- Forks
- 3.1k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Going to list here missing `config.yml` validations that I encounter. Feel free to add more.
- [x] Unique fields names #3804
- [x] Widgets specific field configuration #3841
- [x] Unique file names (https://github.com/netlify/netlify-cms/issues/1035) (https://github.com/netlify/netlify-cms/pull/3913)
- [x] Unique collection names (https://github.com/netlify/netlify-cms/issues/1035) (https://github.com/netlify/netlify-cms/pull/3913)
- [ ] Backends configuration (missing `repo`, `app_id` for `implicit` auth, etc.) Related #1693
Contributor guide
Research direction
Start by locating the config.yml validation logic and reviewing the backend configuration requirements mentioned here, especially repo and app_id for implicit auth. Check related issue #1693 for context. Done means invalid backend configurations are rejected with validations covering the missing requirements and tests demonstrate that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100