Rework how validations are saved
Open
Nobody has claimed this yet.
enhancement
good first issue
Nice to have (optional)
Priority: Low
- Dominant language
- Java
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently, validations are only specified by a science tool. To allow for further use, you should be able to create as many validations as you'd like with a unique name to identify them.
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
No files, tests, or entry points are named in the issue. Start by locating how validations are currently specified and saved, then define the persistence changes needed so multiple validations can be created and uniquely named; done means independently saved validations can be identified by name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100