Closed Haehnchen closed 6 years ago
As I see all these kind of files usually copied to .env (Laravel has .env.example file). And usually both of this file with similar content are in project. This makes Go to declaration feature unconvenient - user should every time choose between .env and .env.dist file declaration. I'll try to avoid these issues in future.. maybe. But currently I'll support only .env files.
Other files (.env-development, .env-production...) should probably only taken into account in other features (see #2).
Actually, you can add any files to .env File type. And everything will work.
But after that any Go to declaration call will be with annoying choice...
I added .env.* files support. But they will work only if there is no main .env file in the project. Or, for example current key, which user wants to Go To Declaration, exists only in .env.dist files, when plugin redirects user to declaration in .env.dist file.
Yep, we have .env.local
, .env.production
etc, so we need the wildcard option to work.
@jezmck it has. .env.* by default. and it can be configured in File types setting. Implemented in 0.7.
~It seems that having both stops the wildcard working.~
Apologies, I had at some point added the others to text
files, individually, without the wildcard
Also support
.env.dist
for ENV variables. eg see https://github.com/symfony/flex/blob/master/src/Flex.php#L177