Idea: Simplify exports of response values (with plugin POC)

I found myself quite often repeating exporting variables. Not 'cause they didn’t exists (I used @ref) but aliasing for a better read. See example:

###
# @name foobars
GET http://localhost:8080/

{{
  exports.bars = response.parsedBody.items[0].foo.bars
}}

### with alias
# @ref foobars
GET http://localhost:8080/{{foo}}

### no alias
# @ref foobars
GET http://localhost:8080/anther/{{foobars.items[0].foo.bars}}

To ease this, I wrote this tiny, quick & dirty plugin which adds a new meta data @exports allowing to do same in a one-liner.

###
# @name foobars
# @exports bars = response.parsedBody.items[0].foo.bars
GET http://localhost:8080/

###
# @ref foobars
GET http://localhost:8080/{{foo}}

Could be extended for multiple variables etc. One downside I see is that feature of @ref gets missing/unclear

wyt?

[rngtng]

Closing…

[AnWeber]

Yes I agree with you. I’m already noticing how I’m overloading quite a few people at work with the tool. On the other hand I want to be as much as possible a superset between rest-client and Intellij Http Client and for that reason I already have a lot of additional features. For example, why do I have the variables declaration when I can also use Javascript exports. The support of dotenv configuration and additionally support Intellij *.env.json. I’ll go and see if I can find suggestions for these problems in other projects, languages.