tree-sitter-dockerfile
tree-sitter-dockerfile copied to clipboard
camdencheek
A tree-sitter grammar for Dockerfile
The [RUN](https://docs.docker.com/engine/reference/builder/#run) instruction now supports options. This PR adds support for any future option, in addition to those officially supported at this time (`--mount`, `--network`, `--security`). The value of the...
There seems to be a parsing error here:  And the corresponding treesitter-playground buffer: 
sorry if this is already known ``` RUN echo "foo" \ echo "feh" ### no syntax hereafter due to space after \ above ```
This change adds a Makefile and bindings to more easily build static/dynamic libraries for use in C-based languages. The implementation is intended to be as generic as possible, to make...
The ENV "Alternative Syntax" mentioned in https://docs.docker.com/engine/reference/builder/#env allows values to have spaces and span multiple lines. This is an example highlight before the grammar change:  Notice it breaks after...
Attempting to parse the file ```dockerfile LABEL A=$B ``` where the file contents do not contain a newline results in a segfault. If I run with `-d`, I get the...
The following causes an error: ```dockerfile RUN \ # comment echo foo ``` Whereas none of the following do: ```dockerfile RUN echo foo \ # comment echo foo ``` ```dockerfile...
Hi! Awesome work with this! I know it's relatively hot-off-the-press, but could we get [Docker Heredoc](https://www.docker.com/blog/introduction-to-heredocs-in-dockerfiles/) support?
The Dockerfile reference includes an `escape` directive which lets you set the escape character for the file. This appears to be [fairly widely used](https://sourcegraph.com/search?q=context:global+file:Dockerfile%24+escape%3D&patternType=literal), particularly for Windows Dockerfiles. However, it...
