Skip to content

Commit b236ab7

Browse files
committed
fix(note): fix on code block
1 parent 6de4b4c commit b236ab7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

service_container/injection_types.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -321,10 +321,10 @@ which allow the container to return the newly created service:
321321
// ...
322322
$container->register('app.newsletter_manager', NewsletterManager::class)
323323
->addMethodCall('withMailer', [new Reference('mailer')], true);
324-
324+
`
325325
.. note::
326326

327-
This type of injection require that you add a ``@return static` docblock in order
327+
This type of injection require that you add a ``@return static`` docblock in order
328328
for the container to understand to be capable of registering the method.
329329

330330
This approach is useful if you need to configure your service according to your needs,
@@ -346,9 +346,9 @@ so, what are the advantages?
346346

347347
The disadvantages are:
348348

349-
* As the `@return static`` docblock is required by the container to
349+
* As the ``@return static`` docblock is required by the container to
350350
understand that the method return a cloned object, you can
351351
found that adding docblock for a single method isn't adapted.
352352

353-
* As this approach force the container to create a new object
353+
* As this approach force the container to create a new object
354354
once the method is called, you can found hard to debug and test your code.

0 commit comments

Comments
 (0)