From 58d222df957364dd6d12ba65498b33aa0cec00e6 Mon Sep 17 00:00:00 2001 From: Jacob Dreesen Date: Fri, 23 Apr 2021 11:55:40 +0200 Subject: [PATCH] Fix typos in the readme (#15) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5819469..e5b4d68 100644 --- a/README.md +++ b/README.md @@ -71,7 +71,7 @@ class MyTest extends WebTestCase // For only the next call to $apiClient->delete() ServiceMock::next($apiClient, 'delete', function () { - return true + return true; }); // This will queue a new callable for $apiClient->delete() @@ -100,7 +100,7 @@ class MyTest extends WebTestCase So how is this magic working? When the container is built a new proxy class is generated from your service definition. -The proxy class acts and behaves just as the original. But on each method call if +The proxy class acts and behaves just as the original. But on each method call it checks the `ProxyDefinition` if a custom behavior have been added. With help from static properties, the `ProxyDefinition` will be remembered even if @@ -108,5 +108,5 @@ the Kernel is rebooted. ## Limitations -This trick will not work if you have two different PHP processes, ie you are running +This trick will not work if you have two different PHP processes, i.e. you are running your tests with Panther, Selenium etc.