Skip to content
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

Closed
szymon-filipiak opened this issue Oct 1, 2024 · 1 comment
Closed

[Feature] Arbitrary file names #23

szymon-filipiak opened this issue Oct 1, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@szymon-filipiak
Copy link
Contributor

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:

Screenshot 2024-10-01 at 3 06 19 pm

In above case database.yaml exists in services 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. See include:

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.

@zavoloklom
Copy link
Owner

@szymon-filipiak It's great suggestion, thanks a lot! I made it possible in v1.0.6

@zavoloklom zavoloklom self-assigned this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants