Skip to content

Commit

Permalink
A few typos and grammar fixes (#1429)
Browse files Browse the repository at this point in the history
  • Loading branch information
aaronsaray authored Sep 15, 2023
1 parent 9ab3aed commit 92ff2d3
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
id: 393
title: "From Symfony to Laravel - Can Laravel even Compiler Pass?"
perex: |
Do you want to migrate your Symfony project to Laravel and not sure if it "handles it"? Switching containers is pretty [straighfowrad](/blog/experiment-how-i-replaced-symfony-di-with-laravel-container-in-ecs) for the most parts.
Do you want to migrate your Symfony project to Laravel and not sure if it "handles it"? Switching containers is pretty [straightforward](/blog/experiment-how-i-replaced-symfony-di-with-laravel-container-in-ecs) for the most parts.
But can Laravel handle as advanced features as compiler passes?
But can Laravel handle advanced features such as compiler passes?
---

Let's take it step by step and list the Symfony container life-cycle. It has 3 separate steps that run one after another:
Expand Down Expand Up @@ -71,7 +71,7 @@ $container->beforeResolving(SomeType::class, function () {
});
```

The callback in 2nd argument will be run before resolving of `SomeType` service. This means when a project needs `SomeType`, it will invoke this closure. But **we don't want to wait for a specific type; we want to call closure before resolving *any type***.
The callback in the 2nd argument will be run before the resolving of `SomeType` service. This means when a project needs `SomeType`, it will invoke this closure. But **we don't want to wait for a specific type; we want to call closure before resolving *any type***.

<br>

Expand Down

0 comments on commit 92ff2d3

Please sign in to comment.