Config options precedence

[moodmosaic]

trafficstars

Now that we merged #397 (and closed #355), perhaps the next step is to have some kind of config precedence.

As in dapp tools and foundry, perhaps, there can be multiple places to specify configuration options, read with the following precedence:

• command line flags
• local Clarinet.toml
• global Clarinet.toml
• locally set environment variables

[lgalabru]

Hi @moodmosaic! In order to help with prioritization, could you help me understand what kind of features / usage could be unblocked with this idea? Thanks!

[moodmosaic]

Off the top of my head

• In the context of #397 and #355, it'd be possible to run clarinet on any folder and instead of an empty session there could be the option to pickup a global Clarinet.toml.
• In the context of #398, it'd be possible to have clarinet run each property/fuzz test 2000 in CI build(s) and 100 times in dev/local build(s). (Configurable.)

A low priority item for now, but worth coming back to it once there's a first draft of #398 out.