filesystem request storage

[kovalvalerii]

Hello Huachao Mao,

Here is the approach I use to run requests on few target env. to different apis with different credentials:

1. plugin env. variables contain "dev"/"beta" etc. urls and user credentials.
2. request files contain specific api calls divided by CRUD methods (for example Entity1 CRUD calls are stored in entity1.http file).
3. .env file contains actual global settings shared between all request files in a folder.
4. each request file loads required data from .env file similar to
   @authtoken = {{$dotenv authToken}}
   @tariffId = {{$dotenv tariffId}}

The only issue I have is the problem with storing "get token" response in the .env file variable when I need to switch to new env.
Now I do next:

1. call get token request to get the token.
2. store the token to file X.
3. run a script to get the token from X and put it to .env

Now the @authtoken = {{$dotenv authToken}} line is ready to get updated token and to use it in any request from the folder.

Idea:
I'd like to propose to add posibility to save response value in .env file as a var
{{$dotenv authToken}} = {{login.response.body.$.type}} {{login.response.body.$.accessToken}}

similar to setting a file variable:
@authtoken = {{login.response.body.$.type}} {{login.response.body.$.accessToken}}

The action will run each time we get positive "login" request result.
To update any .env var after the line changes (for ex. => {{$dotenv authToken11111}} = {{login.response.body.$.accessToken}} )
the end user must run the request again.
I guess it's the simplest way to implement the feature.