don't check path is an actual file #493
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ndeloof
force-pushed
the
soft_validate
branch
from
e6a2cbc to
29b9936
Compare
Signed-off-by: Nicolas De Loof <[email protected]>
ndeloof
force-pushed
the
soft_validate
branch
from
29b9936 to
5873718
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
after #490 I changed my mind, considering this use-case:
as a team has a compose.yaml file, developers have
developsection set, but ops only rely on published images, the latter won't be able to runcompose upas they will get watch.path validation error, which isn't relevant for their usage.So, better check valid path when actually used by some command.