Skip to content

Conversation

Guikingone
Copy link
Contributor

As Symfony isn't an MVC framework but a Request/Response one (see #8153 (comment)), the name of the class which handles the Request isn't forced to contain Controller, it's probably more a common usage than a need to make Symfony works.

@javiereguiluz
Copy link
Member

@Guikingone well spotted! This is not a hard requirement.

@javiereguiluz javiereguiluz merged commit 5b29f5b into symfony:4.0 Feb 18, 2018
javiereguiluz added a commit that referenced this pull request Feb 18, 2018
This PR was merged into the 4.0 branch. Discussion ---------- Controller naming habits As Symfony isn't an `MVC` framework but a `Request/Response` one (see #8153 (comment)), the name of the class which handles the Request isn't forced to contain `Controller`, it's probably more a common usage than a need to make Symfony works. Commits ------- 5b29f5b Minor reword 2b61e3b suggest(Controller): suggestion about naming habits
@xabbuh xabbuh added this to the 4.0 milestone Feb 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

5 participants