-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Arbitrary file names #23
Labels
enhancement
New feature or request
Comments
zavoloklom
added a commit
that referenced
this issue
Oct 1, 2024
zavoloklom
added a commit
that referenced
this issue
Oct 1, 2024
zavoloklom
added a commit
that referenced
this issue
Oct 1, 2024
zavoloklom
added a commit
that referenced
this issue
Oct 1, 2024
zavoloklom
added a commit
that referenced
this issue
Oct 1, 2024
zavoloklom
added a commit
that referenced
this issue
Oct 1, 2024
@szymon-filipiak It's great suggestion, thanks a lot! I made it possible in v1.0.6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
Enable the tool to run checks against any arbitrary file provided by the user and skip regex pattern matching for those files.
Problem this Feature Will Solve
Currently, if a user passes a Docker Compose file to the program that does not match the regex file name pattern, it is ignored. For example:
In above case
database.yaml
exists inservices
directory and is a compose file, however the tool skips validation.This feature will allow users to lint any file they wish, which is particularly useful for modular Docker Compose setups where services are stored in separate files and included in a central
docker-compose.yaml
file. Seeinclude:
Proposed Solution
Add a pre-search step to determine if the file passed by the user is a directory or a file. If it is a file, add it directly to the
filesToCheck
list without applying regex matching.Alternatives Considered
None.
Additional Context
Feel free to reach out if you have any questions or need further assistance.
The text was updated successfully, but these errors were encountered: