You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, dockerfile-utils cannot account for syntax extensions introduced with BuildKit causing false-positive error reporting with the example given below...
The second line causes dockerfile-utils to return Unknown instruction: INCLUDE+dockerfile-utils(38)
Proposal
Introduce the ability to (similar to ShellCheck, for instance # shellcheck disable=SC1083) selectively disable linting errors (specific or otherwise) for a block of instructions
Something along the lines of the example given below would be neat!
The line of the instruction that introduced the error will now be
recorded in the diagnostic itself. This will allow us to implement #106
by checking to see if there is a comment directly above the source line
of the diagnostic.
Signed-off-by: Remy Suen <[email protected]>
@kwvg@muuvmuuv The change to support # dockerfile-utils: ignore comments have been published and released to npm in today's 0.12.0 release. Perhaps you have already moved on to a different linting library but I thought I would let you know anyway.
Description
Currently,
dockerfile-utils
cannot account for syntax extensions introduced with BuildKit causing false-positive error reporting with the example given below...The second line causes
dockerfile-utils
to returnUnknown instruction: INCLUDE+dockerfile-utils(38)
Proposal
Introduce the ability to (similar to ShellCheck, for instance
# shellcheck disable=SC1083
) selectively disable linting errors (specific or otherwise) for a block of instructionsSomething along the lines of the example given below would be neat!
The text was updated successfully, but these errors were encountered: