DataTalksClub / DataTalksClub/website
GAP-1: package config declare has no validation vocabulary (D0.1b blocking gap)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Blocking gap for D0.1c, found by the D0.1b inventory. The site's 31 operational-setting declarations carry validator callables (_bounded_int(min,max), _one_of(...), _url(schemes), _sender, _origin). The released community_base.config.declare (v0.3.0) has only value_type coercion plus an is_email flag — a within-type out-of-range value coerces cleanly package-side. Until the package grows a validation vocabulary (bounded int with min/max, choice set, URL schemes), validation must stay adapter-owned: the D0.1c shim runs the site validator callables after package coercion. Evidence: _docs/adoption/settings-contract-inventory.md GAP-1; core/tests/test_community_base_config_parity.py documents the coercion behavior.
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
Read _docs/adoption/settings-contract-inventory.md for the 31 operational-setting validators, then run core/tests/test_community_base_config_parity.py to confirm the current coercion behavior. Trace community_base.config.declare and define the validation vocabulary needed for bounded integers, choice sets, and URL schemes; done means the package supports these constraints while the D0.1c adapter can use them instead of owning validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100