Add feature: specifying env file

[Rockheung]

Hello! This plugin is fantastic.

This pull request (PR) introduces enhancements to the way the dotenv file is imported, giving users the flexibility to choose any dotenv file that starts with .env. If no filename is specified, the default dotenv filename remains as .env.

Additionally, I have made updates to the readme file.

Please let me know if you have any further suggestions or if there's anything else I can assist you with!

[Xenion1987]

I'd like this feature as well.

[coma-toast]

This feature would greatly simplify configuration for my use case. I am trying to use this instead of (or at least to augment) Postman so that all API calls are documented in our repo, and tracked via git. Using custom variables repeatedly using one parent .env instead of copying and pasting in each folder/file would be a huge improvement.

[Diabl0570]

Do I understand correctly that this only supports a the direct parent dir? Or can this also go up multiple directories?

[Huachao]

@Rockheung could you please resolve the conflicts?

[Rockheung]

While trying to resolve the conflicts, the PR was unintentionally closed. Although it’s late, I have now resolved the conflicts and am reopening the PR.

[Rockheung]

Do I understand correctly that this only supports a the direct parent dir? Or can this also go up multiple directories?

It checks the parent directories step by step starting from the current path of the HTTP file, until it reaches the root directory of the current project.