Doesn't seem to properly support VCL snippets

[nuttmeister]

Doesn't seem to properly support vcl snippets in the sense that they are not inside a sub xxxx {} bracket.

Will produce unexpected token on the first char be it and if statement or similar.

[acme]

Thanks for the report. We'll see what we can do.

[broose-goose]

Any word on this? You could probably make a special rule for NAME.snippet.vcl for special case handling

[corytheboyd-smartsheet]

Adding my plus one to this. The extension is advertised as supporting snippets, but it doesn't actually support snippets.

[alexkli]

Running into this as well. The challenging part is how to tell the extension what vcl subroutine the snippet belongs into, if there are no sub vcl_* statements in the code itself, so that it can autocomplete and lint correctly. There is probably no standard pattern vcl snippet files.

In my case I am currently annotating snippet files with "header" comments:

# type: deliver
# priority: 100
# id: tMPixrYP04Os5DnHevR6B5

unset resp.http.server;

Not sure if this would work for others/the extension though.