Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I install this is valid,but only env.example is valid and highlight. .env is not valid #34

Open
aoxiaoxi opened this issue Jan 24, 2019 · 9 comments
Labels

Comments

@aoxiaoxi
Copy link

I install this plugin first time ,env.example and .env is valid and highlight. but phpstorm's event log say like reconvert file,I click that button.and then .env is not valid.
so I unstall plugin and install this plugin again。but .env is not valid, only env.example is valid and highlight.
help me ,thanks!

@aoxiaoxi
Copy link
Author

.env.example
image
.env
image
why did it happen?

@adelf
Copy link
Collaborator

adelf commented Jan 24, 2019

Please check

@aoxiaoxi
Copy link
Author

it worked ! thank you!

@adelf adelf added the question label Jul 29, 2019
@drawgas
Copy link

drawgas commented Aug 8, 2019

Can't seem to make it work for deeper level .env files. While for the main .env it works perfectly

image

image

@adelf
Copy link
Collaborator

adelf commented Aug 8, 2019

Hi @drawgas .
image
Maybe you somehow marked this file(file type) as a text file?

@drawgas
Copy link

drawgas commented Aug 9, 2019

You were absolutely correct, thanks for pointing that out 👍

@gentax
Copy link

gentax commented Apr 21, 2020

when I updated webstorm to latest release 2020.1, it reassigned .env to text file type, even if it was listed to .env
I deleted it from text and it worked well again

@LexSombra
Copy link

when I updated webstorm to latest release 2020.1, it reassigned .env to text file type, even if it was listed to .env
I deleted it from text and it worked well again

Thanks, worked perfectly!

@BeQ
Copy link

BeQ commented Mar 18, 2021

i do not use .env file, but .env.local/.env.stagin/etc, so i've added .env.* pattern in File Types.
the code highlighting works perfectly, but there is no code completion (for example in env() function).
any ideas?

to be clear: if i have .env file the code completion works fine, but not for the other env files.
so my suggestion/feature-request is: parse all env files and combine keys (because for different environment you can have different set of variables) or, at least, have the possibility to choose the file to be used as reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants