Tested it with common gRPC cases. Just some things why it's not good for gRPC:
1. It doesn't support streams.
2. It doesn't support "include directories" option.
3. It doesn't support Server-Side/Mutual TLS with custom
certificates.
4. When I entered URL like 0.0.0.0:4000 app freezes and won't work, so I can't send any request.
5. I think it support only gRPC-Web, because my URL 0.0.0.0:4000 converts to http://0.0.0.0:4000. If yes, it only covers gRPC-Web that is not fit all user needs.
Include directories is an option which defines paths for your imports in protobuf files. In large projects it's commonly use case when you have directory of protobuf types that used in another files with service definitions for example.
> Our gRPC is not final yet, but improvements are coming!
You do the great project, I tested HTTP features and they looks good! I'm sure that you will improve gRPC experience soon. Thank you for your comment, I will subscribe for your updates!
I like that a lot of projects enters gRPC world - this promotes gRPC and making it easy to use.
Tested it with common gRPC cases. Just some things why it's not good for gRPC: