-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Migrate routing to Symfony #465
Comments
As you already labelled it, this should wait until routing in the core is more finalised. Currently routing is in a state where it could all change from day to day. |
I've used it in two modules, but I'm not sure about it's finalization yet. I'm just hoping that if @cmfcmf changes it, that it won't be too hard to adjust what I have. |
It's important to realise there is no longer any need to follow the whole module, type, func format anymore. There should only be one route to any resource so So basically a module can publish any routes it likes and we just need a convention so as not to collide. |
This feature has been implemented. See the following changes: |
Currently the generator uses a custom Routing class. This should be changed in order to support routing by Symfony2.
Also the handling of different output formats should be updated to use the mechanism Symfony offers for this.
Structural problems in the generator which should be cleaned up in the same step:
Approach for reorganisation:
Advantages:
Cleanup:
legacy controller type
) in the query stringtheme
parameter is not being added to any routes, but assigned as additional parameter so that it becomes part of the query string instead of the route itselflct
inside the templates (pathes like:Resources/views/Post/display.tpl
)Add new routing support:
_format
parameter, remove helper plugin for setting the content type)Examples for cleaned signatures:
The text was updated successfully, but these errors were encountered: