Make sure IDs start with origin in submitted data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The schema suggests that all id fields should start with the value of the origin field, followed by a colon :, but nothing actually validates that. It would be a good step towards protecting the integrity of the data to actually validate that it does, either via JSON schema in kcidb-io (if possible), or by other means in kcidb.
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 inspecting the JSON schema and validation paths in kcidb-io, then check how submitted data is currently validated elsewhere in kcidb. The work is done when submissions with an id that does not begin with the origin followed by a colon are rejected, with coverage for valid and invalid cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100