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

linter: lint rule for using the legacy key/value format with whitespace #4923

Merged
merged 1 commit into from
May 30, 2024

Commits on May 30, 2024

  1. linter: lint rule for using the legacy key/value format with whitespace

    The `ENV` and `LABEL` commands both support using either a whitespace
    delimited token or one delimited with the equals token. The equals token
    is preferred because it is more explicit and less ambiguous than using
    whitespace. The linter rule emits a warning when it sees the whitespace
    separator used.
    
    To facilitate this, the parser was modified to include the separator as
    a node in the tree. The associated parsing code has also been changed
    for 3 arguments instead of only 2 per key/value pair.
    
    Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
    jsternberg committed May 30, 2024
    Configuration menu
    Copy the full SHA
    6cfa459 View commit details
    Browse the repository at this point in the history