Justin Marshall

I was struggling to get this to work in our production build so i cloned the examples to see if i could make my own mono repo and getting it...

@alexeagle you are so quick... thank you... worked perf... going to work on converting our production web build file now.... 🤞

FYI... asked a related question in the bazel slack and it seems that there is some known weirdness with how react-scripts calls eslint under the hood.

can you clarify what it is you are expecting? are you saying that your apollo server response has the pagination in the response header? this feels like an unexpected pattern....

According to the protobuf spec the array structure is acceptable for multiple option names. Is there any word on whether or not protobufjs plans to respect that spec? when loading...

Is there a reason that this is not being addressed? In earlier versions it was the the "[" that threw the error. But this is valid proto definition https://protobuf.com/docs/language-spec#resolving-option-names dependencies...

from the protobufjs docs on resolving optional names, here is an example that i don't see captured in your tests... [https://protobuf.com/docs/language-spec#resolving-option-names](https://protobuf.com/docs/language-spec#resolving-option-names) ``` option (google.api.http) = { custom: { kind: "FETCH"...

@kpritam-tw did you ever find a solution? I have only been able to get it working by refactoring my proto definitions to use the original verbose format for declaring multiple...

i think the problem is that i'm consuming proto source files from a backend service i don't own... so i can't just move files around. using those files more as...