@@ -180,16 +180,16 @@ You can override this behavior as follows::
180
180
181
181
These are all the possible behaviors:
182
182
183
- * ``ContainerInterface::EXCEPTION_ON_INVALID_REFERENCE ``: throws an exception
184
- at compile time (this is the **default ** behavior);
185
- * ``ContainerInterface::RUNTIME_EXCEPTION_ON_INVALID_REFERENCE ``: throws an
186
- exception at runtime, when trying to access the missing service;
187
- * ``ContainerInterface::NULL_ON_INVALID_REFERENCE ``: returns ``null ``;
188
- * ``ContainerInterface::IGNORE_ON_INVALID_REFERENCE ``: ignores the wrapping
189
- command asking for the reference (for instance, ignore a setter if the service
190
- does not exist);
191
- * ``ContainerInterface::IGNORE_ON_UNINITIALIZED_REFERENCE ``: ignores/returns
192
- ``null `` for uninitialized services or invalid references.
183
+ * ``ContainerInterface::EXCEPTION_ON_INVALID_REFERENCE ``: throws an exception
184
+ at compile time (this is the **default ** behavior);
185
+ * ``ContainerInterface::RUNTIME_EXCEPTION_ON_INVALID_REFERENCE ``: throws an
186
+ exception at runtime, when trying to access the missing service;
187
+ * ``ContainerInterface::NULL_ON_INVALID_REFERENCE ``: returns ``null ``;
188
+ * ``ContainerInterface::IGNORE_ON_INVALID_REFERENCE ``: ignores the wrapping
189
+ command asking for the reference (for instance, ignore a setter if the service
190
+ does not exist);
191
+ * ``ContainerInterface::IGNORE_ON_UNINITIALIZED_REFERENCE ``: ignores/returns
192
+ ``null `` for uninitialized services or invalid references.
193
193
194
194
Avoiding your Code Becoming Dependent on the Container
195
195
------------------------------------------------------
0 commit comments