validity check for "bonus" settings in the configuration
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 230
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
The value of "quantity_hits_more_than" should be updated per each study. It is recommended to use a number close to 50% of HITs.
The master script should check out the values of "allowed_max_hit_in_project" and "quantity_hits_more_than" from the configuration file to make sure that they make sense (are in range depending to the study) and show a warning message if not.
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
Locate the master script and the configuration entries for "allowed_max_hit_in_project" and "quantity_hits_more_than". Determine the valid ranges for each study, then add a warning for values outside those ranges; done means the script checks both settings and reports invalid values.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100