commit a4e0be898bc81cdbf96731336cb41ff03a6b1cc5
author Abseil Team <absl-team@google.com> Mon Dec 19 08:27:30 2022 -0800
committer Copybara-Service <copybara-worker@google.com> Mon Dec 19 08:28:01 2022 -0800
tree 7602ac9db708fcf43d7c932a919534d62f6d4aed
parent 3fa7f983c69f780378b4d1ad44d36030ca951ba6

Specify a name for a `Property` in a code example.

It is good practice to specify a name for the `testing::Property` matcher's use in diagnostics, and we should do so in our examples.

PiperOrigin-RevId: 496406309
Change-Id: Ibb4d1ba63771b5d6855442b91564027cda8ddaca

docs/gmock_cook_book.md

diff --git a/docs/gmock_cook_book.md b/docs/gmock_cook_book.md
index 6a795ec..7672457 100644
--- a/docs/gmock_cook_book.md
+++ b/docs/gmock_cook_book.md
@@ -904,7 +904,7 @@
 using ::testing::Property;
 
 inline constexpr auto HasFoo = [](const auto& f) {
-  return Property(&MyClass::foo, Contains(f));
+  return Property("foo", &MyClass::foo, Contains(f));
 };
 ...
   EXPECT_THAT(x, HasFoo("blah"));