[ticklemyelmo]

Why are all of the API clients so intent on storing all your requests and environment config in the cloud?

We would keep a directory of relevant collections and environments inside all our application repos, so they would simply be committed along with the code, be versioned, included in PR reviews, etc. But it looks like all of the popular REST client tools use some hidden cloud services. This is also terrible from a security perspective, since environment variables are likely to include secrets.

[jelling]

And it causes a completely unnecessary versioning problem since the API client code lives separately and not even in a repo typically.

There’s a VSCode extension that executes REST and GraphQL queries stored in a plain text file. So much simpler and more secure. I forget the name - maybe REST client?

[bdeshi]

> I forget the name - maybe REST client?

yes. `humao.rest-client`

[latonz]

Kreya[1] does exactly that. It stores all it‘s data in easy diffable text formats in the filesystem. Currently kreya is limited to gRPC. However, REST support should land soon.

Disclaimer: I‘m one of the creators of Kreya.

[1]: https://kreya.app

[politelemon]

It's easier to monetize that way. They manage the convenience, your team pays them money. Once your team is using it, you're soft-locked in to continue using it.

Yes, agreed on the security perspective. It's not a secure tool. For that you should consider a desktop client (eg Fiddler) rather than a browser based client