Matthieu Coudron

It's possible to see the issue using the following json file ``` { "_categoricalParams": [ { "allLevels": [ "one", "three", "two" ], "currentLevel": "one", "description": "", "name": "cat_param1", "reference": ""...

apparently fixed by https://github.com/rest-nvim/rest.nvim/pull/125 (haven't tested)

feel free to reopen if you still have the issue.

I had started writing a similar script but instead of the `{% %}` approach I was using `> /my_script.sh`. Your PR looks better so I tried it, one issue I...

another complaint is that I would like utils.replace_vars to be able to use the variables set via `context.set_env` which doesn't seem to work yet: For instance I set MODEL_PI in...

For the second issue, I would like utils.replace_vars to take into account the updated "context", https://github.com/rest-nvim/rest.nvim/blob/3c49a8cbf075ff49260402e7ec4ce27814fc89b3/lua/rest-nvim/request/init.lua#L70 I think utils.replace_vars should accept a dict of variables to use, which I've tried...

sure !

Just a note to myself, it would be nice to have a command to dump the env seen by rest-nvim. As for this MR, I think I have an issue:...

is that some kind of standard or just this vscode extension's format ?

also I think the help should mention the post payload must be in a new paragraph apart from the headers ``` 3. Now, we set the body of our request....