Support for env files
This pull request proposes support for .env files. Maybe it has too much features for the daily usage for these kind of files, but I think it's something to be discussed. As the feedback progresses I can add more unit tests.
Implementations :
- mime provider for .env files
- coloring support
- coloring options for keyword like values (null, true, false ...)
- interpolated env key features like completion and declaration finder
- partial ticket fix #6677 covering env files
- hints for duplicate key assignment
- important file node inclusion for .env file for web and php projects
^Add meaningful description above
Click to collapse/expand PR instructions
By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -
- are all your own work, and you have the right to contribute them.
- are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).
Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.
If you're a first time contributor, see the Contributing guidelines for more information.
If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.
PR approval and merge checklist:
- [ ] Was this PR correctly labeled, did the right tests run? When did they run?
- [ ] Is this PR squashed?
- [ ] Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
- [ ] Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?
If this PR targets the delivery branch: don't merge. (full wiki article)