Venom: Support for .yml & .yaml extensions #495
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.
Observation
For this PR I started from an observation:
By default,
venom
CLI take in account .yml extension.If it found .yml file, no need to specify them in the
venom run
command line:But it does not support .yaml extension file:
But:
And: « no yaml file selected », the text message is not very true because we have a YAML file but not in the extension it wanted to :) .
Sometimes in the code we supports both:
But not in the example I show previously for the
venom run
command support by default.Solution
So I recommend that Venom need to supports both .yml and .yaml extensions, not only .yml by default, all the time.
New behavior after the feature coded in the PR
Both .yml and .yaml are now supported by default: