-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add 2.0 upgrade docs #128
Add 2.0 upgrade docs #128
Conversation
doc/upgrade/2.0.md
Outdated
services from legacy bridge. | ||
|
||
* Most of the services have been marked as private in Symfony DI container. | ||
You should not fetch them from container directly any more, instead, inject |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
anymore? instead inject
doc/upgrade/2.0.md
Outdated
You should not fetch them from container directly any more, instead, inject | ||
them as constructor arguments into your services. | ||
|
||
* HTTP 404 error conversion in legacy mode `false` siteaccesses is now turned |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
something like this might be easier to grasp:HTTP 404 error conversion when legacy mode is
false in given siteaccesses is now always handled by Symfony, and config option to control this has been removed so the logic follows legacy mode setting. If you have ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides nitpick, +1
3e7728f
to
81f9df7
Compare
81f9df7
to
716b9e5
Compare
@andrerom Fixed both nitpicks. |
And this one made the other PR much more clear (which is why dealing with dev doc in same PR as code is sometimes a good thing ;)) |
;) |
Documents upgrading to 2.0, specifically:
#122
#126
#127