Add support for a yaml (.yml) config file #24
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Though currently not really needed we are looking at adding some abilities later, specifically integration with Browserstack which will require the ability to set many more options and values.
For a user to manage this in environment variables alone was felt unwieldy, so this change adds support for specifying configuration in a
.yml
file as well as retaining support for environment variables.Subsequent features can then build on this change to add more flexibility, by allowing users to specify options for Quke to use or pass on in the config file.