JetBrains have had support in their IDEs for http/rest files for years. Their implementation differs from the VSCode REST Client extension. VSCode has another extension, httpYac, that provides yet a third implementation that borrows from both of the others. Now Microsoft adds a fourth variant that's different from any of those. These are the implementations I'm aware of, but I'm sure there's others. They all get enough the same to make you think we've got something great, but then they don't get enough the same to really use this across IDEs, editors and command line. Everyone needs to stop, get together and create a standard that can exist across these tools.
Things from each that should be in such a standard.
- Support for pulling variables out of environment files... especially a private file that won't be checked in to version control.
- Support for variables within the http file itself.
- Support for naming requests and defining request dependencies.
- Support for JavaScript blocks. This means support for request, response and client objects need to be standardized.
- Favor JavaScript over "magic". There's no need for a {{$guid}} magic variable if JavaScript can create a GUID and assign it to a variable. REST Client has a lot of magic to support things like authentication that would have been better left to JavaScript blocks.
- Support unit tests.
Ideally we'd have both IDE/editor support and CLI support for running, but if there's a standard format then third parties can supply the CLI solutions.
[Enter feedback here]
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
JetBrains have had support in their IDEs for http/rest files for years. Their implementation differs from the VSCode REST Client extension. VSCode has another extension, httpYac, that provides yet a third implementation that borrows from both of the others. Now Microsoft adds a fourth variant that's different from any of those. These are the implementations I'm aware of, but I'm sure there's others. They all get enough the same to make you think we've got something great, but then they don't get enough the same to really use this across IDEs, editors and command line. Everyone needs to stop, get together and create a standard that can exist across these tools.
Things from each that should be in such a standard.
Ideally we'd have both IDE/editor support and CLI support for running, but if there's a standard format then third parties can supply the CLI solutions.
[Enter feedback here]
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.