header Content-Type text/* ruins highlighting

[tomquas]

System Information

• Operating System: macos
• Extension Version: 0.2.0
• VSCode Version: 1.69.0
• caddy Version: 2.5.2

Describe the bug i defined the section below to import from host specs:

(encode) {
  encode {
    gzip
    zstd
    match {
      header Content-Type application/json*
      header Content-Type application/protobuf*
      header Content-Type application/javascript*
      header Content-Type text/*
    }
  }
}

the last header statement's text/* ruins highlighting such that all following statements are shown without coloring. By moving that line up and down you can track the effect to this part of the header statement.

Expected Behavior Keep highlighting going.

[matthewpi]

I'm not sure I can reproduce this. Here is how that content is highlighted for me .

[tomquas]

hmm, can i ask what theme you're using? here's a shot of my view on this...

[francislavoie]

Are you sure you're using the Caddyfile syntax highlighting? Check the bottom-right of your IDE, does it say "Caddyfile"?

Looks like the /* is being parsed as a comment, but /* is not a comment in the Caddyfile, so it must be from some other language.

[tomquas]

you're totally right. and i feel stupid...

the file was named 'Caddyfile-dev' and VS chose the Groovy highlighter. copied to file to 'Caddyfile' and all works well. sorry.

is there a way for the plugin to register 'Caddyfile*' for caddy-style highlighting?

[matthewpi]

is there a way for the plugin to register 'Caddyfile*' for caddy-style highlighting?

I believe there is a manual file association option you can set, otherwise I could add the association to the extension by default.

[francislavoie]

FWIW I'd appreciate having Caddyfile* work too, but it should exclude caddyfile.go and caddyfile.md which tend to come up reasonably often in the Caddy codebase and docs.