[Proposal] Change name of envoy file - remove .blade.php extension

[allmarkedup]

First let me just say that I'm loving Envoy so far. Great little tool.

So consider this a minor nitpick, but the filename 'Envoy.blade.php' seems overly verbose to me, and also really exposes details about the file that is of no interest - I don't need to know that it is a Blade (-like) syntax file, or even that it's PHP to be honest.

Just something like calling it '.envoy' or plain 'Envoy' or similar would be simpler, and more inline with other tools like Capistrano etc.

Just a thought :-)

[codeclown]

+1

[taylorotwell]

The reason I chose Blade is because many Laravel users have a Blade syntax-highlighting plug-in installed to their editor, and that works based on the file extension.

[brayniverse]

Is it possible to have a config file where a developer can specify their envoy filename? That way people with the extension installed can use .blade.php.

[spamoom]

I agree with this, just Envoy would work very well, and it's only 2 clicks in most editors to set the syntax default for a filetype

[taylorotwell]

I don't want to lose the Blade syntax highlighting.