-
Notifications
You must be signed in to change notification settings - Fork 15.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open source protobuf gmock matchers #3142
Comments
This has been opened since 2017, and there are many disparate fragments and variations of the proto gmock matchers floating around. It would be great to have an officially maintained version. Are there any plans to do this? |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
Has there been any progress on this? |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
Hello, The reason that this hasn't been done after all this time is due to a slightly-weird ownership model. Matchers like I think the right way to think about this is that the core GoogleTest shouldn't need to know about protobufs. If anything, Protobuf should depend on GoogleTest, instead of the other way around. Internally within Google though, GoogleTest folks are the ones supporting matchers like Expanding a bit on what I mean by "lockstep changes": imagine there is a single change in GoogleTest that necessitated changes in something like I think this is something we want to open source eventually, because Google is using/starting more and more third party projects -- and not being able have |
This seems related to google/googletest#1761 |
Hey folks,
Is it possible to open source the protobuf gmock matchers?
Thanks,
Rohit
The text was updated successfully, but these errors were encountered: