-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run collection containing gRPC Requests #11583
Comments
I also need this feature. |
++ from my end as well. I also need this feature for testing my use case related to gRPC Client & Server streaming. |
Hello! I also need this feature. |
This is very, very, very annoying because this is the most used feature in the REST API type. It is almost not usable to test GRPC services |
I also need this feature. |
+1 |
+++ |
+1, need too, would like pay for it |
Hi Everyone )) |
+1 |
+1 (+ add the ability to choose whether to terminate a stream or not before executing subsequent requests) |
+1 for this feature:
|
+1 |
Hi all! Cool feature. I really need this one too)) ++ |
Hello! I also need this feature. |
yeah this would be super useful +1 |
Being able to automate the running of our collection against our gRPC API is critical for us to continue using Postman. Without this feature we are having to consider alternatives. |
+1 |
+1 would love this for our team. We use Postman exclusively with our APIs and are transitioning more of our end points to use GRPC. This is a great feature to test low limit rate limits. |
+1 |
+1, I would love to have this feature |
very good feature, it will be great to have it in the app |
+1 |
1 similar comment
+1 |
+1 |
2 similar comments
+1 |
+1 |
Big up! +1 |
+1 |
7 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
I would appreciate this feature too. +1 |
+1 |
1 similar comment
+1 |
Is there an existing request for this feature?
Is your feature request related to a problem?
The inability to run the collection containing the gRPC requests prevents me chain testing the gRPC requests.
Describe the solution you'd like
The solution should be identical with the one implemented for the REST API Collection, which is right-click on the collection and then select the Run collection option.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: