- Notifications
- Fork 27.7k
-
Star 159k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decorate .env.* files in the file explorer the same way as standard .env files #149681
Decorate .env.* files in the file explorer the same way as standard .env files #149681
Comments
gjsjohnmurray
commented
May 17, 2022
Looks like a couple of years back the Docker extension authors went down a similar path and it wasn't entirely smooth. microsoft/vscode-docker#1908 |
devuxer
commented
May 17, 2022
@gjsjohnmurray , Looks like it did ultimately get merged, though, right? And in this case, I don't think there's any special editor involved (.env files seem to be treated as plain text files). |
lramos15
commented
May 18, 2022
This is up to each file icon theme to implement. Our default theme is the seti icon theme so feel free to open the request there. It doesn't appear they have glob support though making this case hard. I've unconsciously started naming my files |
devuxer
commented
May 19, 2022
Thank you. In case anyone wants to track this: jesseweed/seti-ui#652 |
lramos15
commented
May 19, 2022
In the end I don't think they can do that without listing every possible .env we have this feature request actually which isn't easily implementable #12493 |
devuxer
commented
May 19, 2022
That issue is an interesting read. Perhaps just a list of the most common .env.* examples would be at least better than the status quo of only .env. |
I get that this is a really microscopic feature, but any chance we can get all .env.* files (like .env.development, env.production, .env.local, .env.local.development, etc.) to show the same cog wheel icon in the file explorer as files named .env? This would make them all appear like they belong together, and, well, it would look nicer (and not look like we named our file incorrectly).
I suppose this is not currently done because .env is one of the few (only?) file extensions where the convention is to put it at the beginning rather than end (which I further suppose is a result of wanting them to alphabetize into a nice group).
The text was updated successfully, but these errors were encountered: