SAdd --stdin and --stdin-filename support (#808) #877
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.
feat(cli): add --stdin support for piping env content (#808)
Closes #808
This change introduces two new flags to dotenv-linter. The --stdin flag allows reading .env content from standard input, while --stdin-filename lets users specify a filename for diagnostic output when piping. In src/cli.rs, build_cli() has been updated to declare these options. In src/lib.rs, the run() function now checks for --stdin and either reads from stdin or from the provided file paths accordingly. Finally, an integration test named stdin_flag_works was added in tests/cli.rs to verify proper handling of piped input.
✔ Checklist:
Commit messages have been written in Conventional Commits format
Tests for the changes have been added (tests/cli.rs)
Documentation on dotenv-linter.github.io has been updated (if applicable)