tree-sitter-dockerfile issues

Incorrect highlighting for certain RUN directives in nvim

4

Hi, I'm seeing some incorrect highlighting for some of the `RUN` directives in this `Dockerfile` in Neovim; ```Dockerfile FROM node:20-alpine AS builder WORKDIR /staging COPY . /staging/ RUN corepack enable...

jason-ci

Trouble with \e sequences in shell strings

I checked that `echo "\e[91m"` is syntactically valid in both Bash and Bourne shell (although it has a different meaning, see my comment at https://github.com/semgrep/semgrep/issues/10068#issuecomment-2057821081). It causes a parsing error...

mjambon

Add support for quoted USER argument

The following is supported by `docker` by the current tree-sitter-dockerfile implementation only supports unquoted strings: ``` FROM busybox USER "nobody:nobody" ```

mjambon

Add ARG support for multiple variables in one instruction

1

The official documentation makes no mention of supporting multiple variables in a single ARG instruction (https://docs.docker.com/reference/dockerfile/#arg). However, the `docker` command supports multiple variables. For example, the following does what one...

mjambon

Problem parsing trailing comment after line continuation

1

Here's some input that causes the parsing error: ``` $ cat trailing-comment.dockerfile FROM busybox RUN ls \ # comment with nothing after ``` It is accepted by `docker` but not...

mjambon

Make language injections easier by making nodes anonymous

2

Without `heredoc_line` and `shell_fragment` being present in a tree it's much easier to add language injections, for example, with bash: ```scm ((shell_command) @injection.content (#set! injection.language "bash")) ((run_instruction (heredoc_block) @injection.content) (#set!...

faergeek