Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Postman Now Supports gRPC

blog.postman.com

Post reply on HN
Print view View original

181–190 of 216 posts

Re: Postman Now Supports gRPC

#181

Post by lysium »

ynouri wrote: post #171

My company’s product is an API and Postman has been a key tool to test it, collaborate internally on requests and share it to the external world. Our ecosystem is also very API intensive and we also use Postman to discover other companies APIs. We use all those features: - HTTP requests - Mock servers (to test async requests which call back a webhook endpoint) - Workspaces: private and public - Monitors, alerts and i…

How do you do version control with your postman scripts? That was the biggest issue on my last project.

Plus, if the API moves, we had to (manually) find and fix dozens of Postman tests.

I'd appreciate it, if you have some insights that can move my team forward.

Re: Postman Now Supports gRPC

#182

Post by piaste »

halpert wrote: post #173
avel wrote: post #158

Earlier quoted context omitted.

This extension also keeps a history of requests. How complicated are your requests? If I need to test a POST request with a JSON payload longer than a line or two, I'll go and construct my curl command in a text editor anyway, since the shell prompt / readline is not easy to edit. Once you need to start escaping single or double quotes or html payloads in the request, it quickly gets cumbersome. At that point I ditch…

You can have curl read the request body from a file using --data @filename.txt.

Which means you've opened an editor already to edit the request. Might as well send the request right there via an editor command/plugin.

Re: Postman Now Supports gRPC

#183

Post by piaste »

teaearlgraycold wrote: post #172
jonfk wrote: post #79

To add another data point, I also moved on from Postman a while ago. Similarly to several commentors here I had found it to have become bloated, slow and buggy imho. In my particular use case, I found the urlencoding when using oauth1 to be pretty buggy. It would sometimes not work on certain headers it generated. My team ended up moving to Paw but that has been a bit problematic since it only supports osx, so some t…

> My team ended up moving to Paw but that has been a bit problematic since it only supports osx, so some team members are also using insomnia One of the first things I learned working professionally is that of it’s possible you need to force all engineers to use the same OS. No one will ever agree on one Linux distro. No one wants to develop on Windows (unless you’re developing for Windows). So you should but everyon…

I am legitimately unsure whether or not your comment is satire of a certain kind of pointy-haired middle managers. If it is, it's very well done.

Re: Postman Now Supports gRPC

#184

Post by CSSer »

jonfk wrote: post #127
CSSer wrote: post #95

Earlier quoted context omitted.

Thanks for sharing. Is the code for httpyac anywhere? I can only find the repo for the docs. I'm trying to check it out, but I encountered some errors when trying it add it as a global with yarn because I'm running a node version greater v14. The extension also gave me a deprecation warning about Buffer() usage.

Here is the github repo for httpyac [1]. Not sure why it's not part of the httpyac org that hosts the site. [1] https://github.com/AnWeber/httpyac

Thanks for that! Sorry, I was in a bit of a hurry earlier. I should've thought to check the commit authors for the site.

Re: Postman Now Supports gRPC

#185

Post by mhoad »

AtNightWeCode wrote: post #165

Left Postman a long time ago after all the stupid decisions. Never looked back. gRPC is a nice addition to Postman though. In contrary to what advocates of gRPC thinks, this kind of development is the key thing to bring gRPC to the wide audience. The lack of test tools for non-developers has been an obvious problem with gRPC. Most people should probably still not use gRPC since it is in most cases useless and causes…

As someone who is about to start a big project with gRPC kind of at the middle of it all would you mind elaborating on the other problems you were alluding to? From the outside and some basic testing it seems great

Re: Postman Now Supports gRPC

#186

Post by ynouri »

lysium wrote: post #181
ynouri wrote: post #171

My company’s product is an API and Postman has been a key tool to test it, collaborate internally on requests and share it to the external world. Our ecosystem is also very API intensive and we also use Postman to discover other companies APIs. We use all those features: - HTTP requests - Mock servers (to test async requests which call back a webhook endpoint) - Workspaces: private and public - Monitors, alerts and i…

How do you do version control with your postman scripts? That was the biggest issue on my last project. Plus, if the API moves, we had to (manually) find and fix dozens of Postman tests. I'd appreciate it, if you have some insights that can move my team forward.

We face a similar situation and we sometimes introduce API changes that break the monitors, which then requires to manually fix the testing script. The pain hasn’t been big enough yet to make us search for a different solution. Note that we are using Monitors mostly for end to end, user like tests, which represents a small fraction when compared to our unit test suite covering the API (where tests tend to be quite E2E as well).

We do use the one way Postman -> Github integration though. Every time a change is done, it is committed to a dedicated Github repo. We use it as a backup in case anybody messes up the scripts

Re: Postman Now Supports gRPC

#187

Post by dschuessler »

mythz wrote: post #19

We've moved on from Postman for our own APIs and are now including an integrated API Explorer into each new .NET v6+ App https://docs.servicestack.net/api-explorer As a consequence of our API Design we're also able to reuse our existing Typed APIs in gRPC services: https://docs.servicestack.net/grpc

This seems to be the golden way of solving the problem Postman is attempting to solve. Have your request collection as code that you can develop with your features and check into your VCS.

I always dreamed of something like this and was more than surprised that it doesn't seem to exist. Does anyone know of a similar solution for node.js?

Re: Postman Now Supports gRPC

#188

Post by sbmthakur »

ROARosen wrote: post #137
dewey wrote: post #18

Earlier quoted context omitted.

I think the killer feature for these separate tools is usually that you can easily do a right click -> "copy as curl" in the network inspector, then import it in Postman/Paw and then tweak parameters / add headers there. This is not really possible in the browser network tools.

On the on Microsoft Edge chromium you can can enable an "edit and resend" feature save the requests to "Collections" and create request environments.

I wonder if a such a feature can be added in Chrome/Firefox with an extension.

Re: Postman Now Supports gRPC

#190

Post by halpert »

piaste wrote: post #182
halpert wrote: post #173

Earlier quoted context omitted.

You can have curl read the request body from a file using --data @filename.txt.

Which means you've opened an editor already to edit the request. Might as well send the request right there via an editor command/plugin.

Or you saved the response from a different curl request, or it’s checked into git, or a million different reasons.
Post reply on HN