Add support for additional .env file locations #29
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.
Closes #27.
This pull request introduces improvements to the environment keys checker by allowing additional locations for
.envfiles to be specified and scanned, refactoring how environment file paths are handled, and enhancing the display of missing keys. The changes increase flexibility for projects with multiple or non-standard.envfile locations and improve the clarity of output.Support for additional
.envfile locations:additional_env_locationsinconfig/env-keys-checker.phpto specify extra directories or files to scan for.envfiles. This allows the checker to work with.envfiles outside the project root or in custom locations.HelperFunctions.phpto aggregate.envfiles from both the default and additional specified locations, supporting both directories and individual files.Refactoring and improved handling of file paths:
envFilePath) in the data passed between actions, improving reliability when handling files in different locations. [1] [2].envfiles are present.Test improvements: