commonform / commonform/commonform-validate
Should immediately adjacent term uses validate?
Open
Nobody has claimed this yet.
help wanted
question
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
For example:
{ "content": [ { "use":"A" }, { "use":"B" } ] }
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 reading the validator entry points and existing tests for Common Form content objects, then compare their treatment of adjacent "use" terms with the JSON example in the issue. Define the expected validation behavior and add coverage for the adjacent-term case before changing implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100