condition_pattern (regex)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 230
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Feature: Move the condition_pattern and condition_key to the configuration file of the master script. The master script should add them to the customized configuration file that it generates for the result_parser script.
pros:
- The customized configuration file of result parser does not need to be edited by the user
- The user deals with the proper setup of condition_pattern in front. In case they need to apply any changes in the URLs of the audio clips they can do it in advance.
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 locating the master script and the result_parser configuration generation. Trace where condition_pattern and condition_key are currently defined and how the customized configuration file is produced. Done means users configure these values in the master script's configuration and the generated result_parser configuration contains them without manual editing.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100