F: Hardcoded values reduce portability - #3
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
Several values in the challenge-f.sh script are hardcoded (such as paths and filenames), which reduces flexibility and makes reuse and testing more difficult.
The script should allow configuration via environment variables while remaining backward compatible.
Acceptance Criteria
- All hardcoded paths and filenames must be configurable using environment variables
- Each configurable value must have a clear and reasonable default
- When no environment variables are provided, the script must behave exactly as before
Notes
- Existing usage must not break
- Defaults should be defined in a single, clear place near the top of the script
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
Open challenge-f.sh and identify the hardcoded paths and filenames near the script's current logic. Run the script once with no environment variables to capture its existing behavior, then verify that configured values change the relevant inputs while unset variables preserve the original behavior. Done means every hardcoded path and filename is configurable with a clear default in one place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100