Add shellscript filenamePatterns for .env*
#173425
Assignees
Labels
feature-request
Request for new features or functionality
insiders-released
Patch has been released in VS Code Insiders
languages-basic
Basic language support issues
verification-needed
Verification of issue is requested
verified
Verification succeeded
Milestone
Comments
alexr00
added
feature-request
|
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
alexr00
pushed a commit
that referenced
this issue
Feb 10, 2023
* Add shellscript `filenamePatterns` for `.env*` In some cases, projects use `.env` files such as `.env.development` or `.env.production` or similar things. Adding this to extensions/shellscript/package.json as a `filenamePatterns` avoids developers having to add specific `"files.associations"` to their VS Code settings files. Fixes #173425 * Change pattern from .env* to .env.*
vscodenpa
added
unreleased
c-claeys
pushed a commit
to c-claeys/vscode
that referenced
this issue
Feb 16, 2023
* Add shellscript `filenamePatterns` for `.env*` In some cases, projects use `.env` files such as `.env.development` or `.env.production` or similar things. Adding this to extensions/shellscript/package.json as a `filenamePatterns` avoids developers having to add specific `"files.associations"` to their VS Code settings files. Fixes microsoft#173425 * Change pattern from .env* to .env.*
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some cases, projects use
.envfiles such as.env.developmentor.env.productionor similar things.Adding this to extensions/shellscript/package.json as a
filenamePatternsavoids developers having to add specific"files.associations"to their VS Code settings files.The text was updated successfully, but these errors were encountered: