Allow provided configuration in the options for loadConfiguration to be a argv-style string, as an alternative to a configuration object.
⚡️ What's your motivation?
Many existing framework integrations using the Cli class use an argv string to pass the options in, and also allow end users to express options this way. This will make it easier for such frameworks to adopt the new API, and it uses existing code that we had for handling configuration files anyway.
🏷️ What kind of change is this?
:zap: New feature (non-breaking change which adds new behaviour)
coverage: 98.383% (+0.004%) from 98.379%
when pulling 3631869e6ab4175b69e4811fcbea099ad94a55b6 on feat/provided-configuration-string
into 53ccc44cb7f60d0f7de2893662f83eac7b60307c on main.
🤔 What's changed?
Allow
provided
configuration in the options forloadConfiguration
to be a argv-style string, as an alternative to a configuration object.⚡️ What's your motivation?
Many existing framework integrations using the
Cli
class use an argv string to pass the options in, and also allow end users to express options this way. This will make it easier for such frameworks to adopt the new API, and it uses existing code that we had for handling configuration files anyway.🏷️ What kind of change is this?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.