Normalize values used to represent true with boolean-esque env vars
- Dominant language
- Haskell
- Stars
- 2.1k
- Forks
- 320
- PR merge metrics
- No merged PRs in 30d
Description
Right now env vars that accept boolean-esque values (like `DAPP_TEST_FFI`, `HEVM_RPC`, and `DAPP_BUILD_OPTIMIZE`) each require slightly different values to represent true.
Sometimes `1` means true, sometimes `yes` means true, sometimes any non `0` value means true, and sometimes the variable being set at all means true!
Ideally all boolean-esque env vars would only accept one of these values to mean true, which would make using them a lot less confusing :p
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating how DAPP_TEST_FFI, HEVM_RPC, and DAPP_BUILD_OPTIMIZE are parsed and compare the values currently treated as true. Then inventory the other boolean-esque environment variables and determine whether they follow the same normalization rule. Done means the relevant variables consistently accept the agreed true representation and their behavior is covered by the existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100