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
deprecate Dockerfiles's getDirective() function as it only ever retrieves one directive
introduce a new getDirectives() function to Dockerfile that returns ParserDirective[]
update the parser to correctly populate getDirectives()
We should have supported getDirectives() from the beginning but did not bother to given that only the escape directive existed when the project was started. Now it is clear that would have been the better path to take.
At the Dockerfile's level, we have no idea whether someone is using the BuildKit backend or not. Although the BuildKit backend is considered to be experimental, given that the syntax directive is directly mentioned in the official channels I think we should support the parsing of it.
The text was updated successfully, but these errors were encountered:
With the introduction of the
syntax
parser directive, Dockerfiles now technically support two parser directives:escape
syntax
We need to:
Dockerfiles
'sgetDirective()
function as it only ever retrieves one directivegetDirectives()
function toDockerfile
that returnsParserDirective[]
getDirectives()
We should have supported
getDirectives()
from the beginning but did not bother to given that only theescape
directive existed when the project was started. Now it is clear that would have been the better path to take.At the Dockerfile's level, we have no idea whether someone is using the BuildKit backend or not. Although the BuildKit backend is considered to be experimental, given that the
syntax
directive is directly mentioned in the official channels I think we should support the parsing of it.The text was updated successfully, but these errors were encountered: