Joshua Carpeggiani

Support gRPC streaming

10

## Feature Description Support gRPC streaming as described [here](https://k6.io/blog/performance-testing-grpc-services/) ## Suggested Solution (optional) The grpc Client currently uses the grpc.Invoke command: https://github.com/k6io/k6/blob/61f464b99a2d052347fee157eb68a024f5cf7430/js/modules/k6/grpc/client.go#L398 Instead of this, possibly using the return value...

Fix/gh 982 line chars

1

So `message` types for filedescriptors field types and (all?) other types seem to use slightly different source code location paths The issue in #982 was that the int32 path did...

buf convert error messages should be more clear when type does not exist in input

1

Expected: ``` buf convert . --from=payload.json --to=- --type=Person Failure: proto: not found ``` Actual ``` buf convert . --from=payload.json --to=- --type=Person Failure: type Person not found in input ```

The `buf convert --from` and `--to` flags both support specifying the format with `#format=[json|bin]` or file extensions. Supporting this for `buf curl` would also be nice and consistent with the...

Promote `buf beta registry` to stable

3

This includes merging all of the `buf beta registry` commands with `buf registry` commands

Type aliases for generics

18

Whenever I'm writing a new connect service it always seems frustrating that it seems like I've got a lot of noise in the function parameter: ```go func (e *elizaServer) Say(ctx...

This seems to error at the moment ```proto message Foo { repeated string field = 1; } ``` `grpctl .... --field="blah"` Currently this gives a nasty json marshalling error To...

Flags should be validated client side with detailed feedback of issues arising if protoc-gen-validate options are found on the proto files. Links: https://github.com/envoyproxy/protoc-gen-validate

Would be nice

should be able to output a json schema just like `grpcurl —message-template`