Refactor: separate schema validation for data processing validation
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
from call 19/02:
- The check data schema function does two checks: data schema validity and data handling processing. We should evaluate to refactor and review the purpose.
- @danielpeintner we can have a helper method to safely call the value function (without catching exceptions).
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 check data schema function and tracing its callers, then review the value function handling discussed in the issue. Done means the schema-validity check and data-processing validation have clearly separated purposes, with a helper for safely calling the value function as appropriate; no tests or files are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100