Replies: 1 comment 1 reply
-
Would you mind opening a pull request with your changes? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
first of all, let me thank you for this amazing tool you've built. I am currently evaluating tools for automating functional tests for a gRPC API and so far, stepci is my favorite candidate!
I've followed the tutorial on testing gRPC with stepci and was able to successfully make a gRPC request to a service which does not use any imports. However, calling a service which imports
google/api/annotations.proto
always fails because this dependency cannot be resolved.Now I know from using other tools like
grpcurl
that I need to specify additional directories (like with option--import-path
ingrpcurl
); however, there does not appear to be a way to do this in stepci (but there should be from what I've gathered from discussions here and here).My knowledge of JS/TS/NodeJS is limited at best, but it seems that
cool-grpc
always passes hard codedloaderOptions
toproto-loader
. I managed to do a local workaround by "enabling" YAML fieldsconfig.grpc.includeDirs
andtests.<test>.steps.[step].grpc.includeDirs
which behave likeconfig.grpc.proto
andtests.<test>.steps.[step].grpc.proto
and "merging" this with the hard codeddefaultLoaderOptions
, but I was wondering if there is another, cleaner way to accomplish this.Best regards
Moritz
Beta Was this translation helpful? Give feedback.
All reactions