Coding Shorts: Sharing Variables in .http Files

[@Kingside88]

Thank you. I learned the "user" part of it. It would be great if somehow it could be possible to get the bearer token by login into identity provider. And then share it across http files

[@swildermuth]

Yeah, I still have to run the web app and steal the token.

[@grumpydeveloper69]

Just like the VS Code Rest Client plugin

[@pilotboba]

It would be nice if it could integrate with the dotnet configuration system as well as the user configuration specified in the project so that you can pull those secrets or user level totally out of the project folder.

[@swildermuth]

It would. You can always do a PR!

[@microtech2448]

Hi, did you find a way to set env variable once you have the result from API, just like in postman. An instance can be, you call login api and get the token, anyone would want to save it automatically in the env variable instead of manually copy paste it.

[@swildermuth]

Yes, in Visual Studio, you can create an environment (see upper right hand corner drop-down) that is used by any http files that choose that environment.

[@LindenMikus]

would be cool if there was a way to convert existing postman collections and environments to these type of files

[@swildermuth]

Since these files are *just* text files of the actual requests, I bet it wouldn't be too tough.

[@torkilpedersen5014]

Like the length of our presentations☺

[@swildermuth]

Glad you like them!

[@DannyHille]

Neat trick - Thanks 🙂

[@swildermuth]

Glad you liked it!

[@roa71]

Thanks. Why moving on from Postman? Better integration with VS or other reasons? Just curious..

[@Kingside88]

Because you dont want to have multiple apps open while coding

[@pilotboba]

A couple of reasons. you can check in the files right next to your code. You can stay in the same app to do tests. Granted you can store a Postman collection in your repo, but its a few manual steps, vs checkout and go, add one, commit, and everyone else gets the new HTTP files to use with your new endpoints.

[@pilotboba]

That said, it doesn't really replace Postman or Insomnia, they have a lot more features that are great if you need them. But for just calling endpoints, passing payloads, and checking responses this works.

[@swildermuth]

It's just text files that look like requests. That's why I like it. It doesn't help you as much, but also doesn't paywall anything. I like that it is simpler (and works in VS and VSCode).

[@peymannaji]

What if I have a POST request and ID is generated in backend and I would like to use that in the GET request? I'm asking this question, because I all the tutorials, ID's are always hard coded.

[@swildermuth]

No real way to do that right now. There is a random parameter but I dont' find it useful.

[@peymannaji]

@@swildermuth Thanks 😊 🙏

[@paddymcsquirrel]

Say you want to generate token and use it subsequently, you can name the first request ( in VS Code, maybe also in VS 20*) as a comment before the request, eg ‘# name @login’, then refer to the response in subsequent requests using, e.g {{login.response.body.token}} (when response body is json), you can separate requests using ###

[@paddymcsquirrel]

So if the id is returned in the response to the first post, it should be possible to use it later

[@paddymcsquirrel]

Also, it may be ‘# @name login’