First of all, thank you for this awesome package.

I have been using this for some time and was able to work around every problem found, but there is something i can't seem to discover which is metadata matching.

In the above sample, i wan't to match 2 requests:
1- Metadata with Culture: 'pt-PT'
2- Empty Metadata

The problem with this is that grpc-mock will always return the first stream instead of throwing the error provided in the second array element. I saw that metadata is implemented for error output responses but not for input.

This is something important for Sad Path tests, i could try to submit a PR, but first i would like to know if this is already possible somehow.

Thanks in advance.

I'm having this problem, when I add the second enum in the message, it returns me the error: INVALID_ARGUMENT

Messases exemple:

`
message RequestGreet {
string message = 1;
repeated Pair metaData = 2;
bytes file = 3;
DocumentSide documentSide = 4;
DocumentType documentType = 5;

}

message ResponseGreet {
string message = 1;
repeated Pair metaData = 2;
bytes file = 3;
DocumentSide documentSide = 4;
DocumentType documentType = 5;
}

message Pair {
string key = 1;
string value = 2;
}

enum DocumentType {
RG = 0;
CNH = 1;
Self = 2;
}

enum DocumentSide {
front = 0;
back = 1;
}

`

Is it possible to specify two protobuf files? I have a GRPC server which has "grpc health-check" and other services.

The case: currently implementation for each request looks though rules at https://github.com/YoshiyukiKato/grpc-mock/blob/master/index.js#L67 and trying to find corresponding rule and output.

If no rule was found, then callback not being called at all. And no exception was raised.
As result current test running process just get stuck (mocha, jest test runner, for example). And you have no idea what's going wrong. Cause your grpc client code expects a ccallback from GRPC at any case. But grpc-mock will not call it in that case.

As a developer, i have only one way out: set a breakpoint at grpc-mock's for loop and find wrong request, that was not able to find proper rule. It'a a headache.

Propose to change the behaviour: if no rules was matched current request, rais an exception.
Similar logic implemented at nock library: https://github.com/nock/nock#expectations

npm WARN deprecated [email protected]: This library will not receive further updates other than security fixes. We recommend using @grpc/grpc-js instead.

Thanks for the great package! Is there a plan to support returning gRPC errors from the mock server? Something like:

  rules: [
    {
      method: "howAreYou",
      input: { message: "Hi" },
      error: {
         code: 5,
         message: "Resource not found",
         data: ... (optional custom data),
    },

That would be quite useful for me..

Hello!

I tried this service last weekend, when I got the mock server up and running, I tested using cURL and got a "Weird server reply"

curl 'http://localhost:8080/s12.iot.v1.DevicesService/ListDevices' -X POST -I
curl: (8) Weird server reply

Do you know if there something obvious I'm skipping?

Cheers!

I am attempting to return an ENUM value as part of an output. I have tried both specifying the value as its string representation as well as its integer representation, but neither seems to be working. Should this work?

Hi,
The README.md could contains details on how to start this mock-grpc locally. I am new to node.js and all I want is this mock server to be up and running. How do I do that?
TIA

hi, has anyone got this package working using some import like "empty.proto" from google ?

i can find theses .proto files in my ./node_modules/google-gax/build/protos/google/protobuf/ folder

But i can't make it work even with includeDirs options like that :
options: {includeDirs: ['./node_modules/google-gax/build/protos']}

syntax = "proto3";

import "google/protobuf/empty.proto";
import "google/protobuf/wrappers.proto";

package myPackage;

Has anyone got an idea ?

Thank you very much

I tried:
{
input: {
param: "^[a-zA-Z]+"
}
}
and I set param to "uuid" in the request , but it doesn't work and throws "io.grpc.StatusRuntimeException: INVALID_ARGUMENT: unexpected input pattern"

Hi,
I have a proto file which uses google.protobuf.FieldOptions and it fails compailing that protobufjs cannot resolve this.
Pasted the error below:
/node_modules/protobufjs/src/root.js:243 throw Error("unresolvable extensions: " + this.deferred.map(function(field) {
Any idea how to make protobufjs support this?
Thanks

Hi, thanks again for your work :)

Sometimes you just care about a part of the input of the request. For example,

Input object: user: String, friends: List<User>, random: Number

pseudo-rules:

• if user: "john" then return blah
• if user: "laura"then return an error

In these cases I don't care about the friends and I can't predict the random number. I know that with strings you can use .* but it doesn't work with other types.

Would it be possible for the server to match like this?

Can you add a LICENSE file to this repo?

• configurable input & output

{
  input: {
    stream: Boolean; //stream or not
    body: Object | string; //raw object or pattern string
  },
  
  output: {
    stream: Boolean; //stream or not
    body: Object
  }
}

Hi, first of all thanks for your work!

Sometimes in the same tests suite you have different tests that need different set of rules, and today the only way to change the rules is starting a new server with those new rules. An example would be expecting the same request to return successfully on one test, and fail on another (the input can't be changed).

Would it be possible to update those rules on the fly so we can make the tests use only 1 server? also making them faster?

Because this lib's code has been complex and dirty.

What is the proper response to specify multiple unary responses based on input pattern?

{
    method: "myMethod",
    input: { param: "one" },
    output: { resp: "two" },
},
{
    method: "myMethod",
    input: { param: "three" },
    output: { resp: "four" },
}

seems to make the server crash as well as return unexpected input pattern

/usr/local/lib/node_modules/grpc-mock/node_modules/grpc/src/server.js:69
  call.startBatch(error_batch, function(){});
       ^

Error: startBatch failed
    at handleError (/usr/local/lib/node_modules/grpc-mock/node_modules/grpc/src/server.js:69:8)
    at sendUnaryData (/usr/local/lib/node_modules/grpc-mock/node_modules/grpc/src/server.js:595:9)
    at HandlerFactory.<anonymous> (/usr/local/lib/node_modules/grpc-mock/index.js:143:15)
    at Object.DeleteDevice (/usr/local/lib/node_modules/grpc-mock/node_modules/grpc-kit/index.js:53:28)
    at /usr/local/lib/node_modules/grpc-mock/node_modules/grpc/src/server.js:590:13