ML4GW / ML4GW/typeo

Parse multiple `${base.x}` and `$ENVIRONMENT_VARIABLE` expressions in each config argument

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Right now config parsing only checks for one base or environment variable per expression. This should be updated to iterate through all possible such expressions

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the Python config-parsing entry point used for each config argument and read how it currently handles a single ${base.x} or $ENVIRONMENT_VARIABLE expression. Update the behavior so each argument handles all such expressions, then verify that arguments containing multiple base and environment expressions are parsed correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.