Consider defining each directive

[isobit]

Consider defining each directive

[mholt]

@isobit makes some good points. Directives are "anything goes" - there's just no good reliable way for the editor to know what will actually work when the user runs Caddy. The editor would need a way to hook into the exact instance of Caddy that will be executed, because every build is different.

So I recommend highlighting words that "should be" directives based on syntax/location.

[isobit]

I mostly made this design decision because of @mholt's recommendation. There are two major issues with enumerating the available directives:

1. Even if building the list of directives is scripted, the build script must be re-run and the plugin updated every time the list changes.
2. The "official" list of directives does not cover directives defined by users who build their own copy of Caddy with custom plugins. The Caddyfile syntax defines directives as arbitrary tokens, not by enumeration.

You have a valid point, though, and I do like the idea of automatically updating the list of directives. Perhaps there is a compromise?