Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

tnguy370
Copy link

@tnguy370 tnguy370 commented Jun 9, 2025

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

The linter finds incorrect diagnostics when there is an inline comment

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.