On 2/23/10 2:09 AM, Jordi Boggiano wrote:
On 22.02.2010 14:40, Thomas Rabaix wrote:
How can we provide feedbacks or open tickets for the Symfony 2 preview ?
I will start here since nobody is answering :)
- I found a typo in the WebBundle/Resources/config/pdo.xml config file,
dsn is spelled dsn:
fixed
That being said, I don't know if that pdo file is used at all so it
might not matter.
- Another question that troubles me a lot is how can I merge a full set
of routes from a bundle to my main project.. I could import them all by
manually writing them one by one like:
blah:
resource: path/to/routing.yml
But that is hardly convenient once the routes start to multiply.
Can you explain why it is not convenient? Most of the time, you will
probably need to prefix them anyway:
blah:
resource: path/to/routing.yml
prefix: blog/
Do you expect to be able to import all routing from all enabled bundles?
But then, in which order? and without any prefix?
Symfony 2 tries to be as explicit as possible.
- Also I would like to try to extend a core class from a random bundle,
namely the RequestHandler\Request class..
I tried to add this to my config.yml, but it totally fails:
foundation.services:
request.class: My\Request
That's possible. You just need to "know" the parameter name for now as
there are not exposed by the extensions... yet ;)
So, to extend the request, you can do something like this:
parameters:
request.class: My\Request
In my opinion this should be possible for *all* services, by default,
without the bundles having to voluntarily expose their classes as
parameters, otherwise the dependency injection is only smoke and mirrors
and only offers as much flexibility as the bundle author allowed. I find
the whole DI thing much more complicated to grasp than the plain one we
used in Okapi because of the multiple layers of abstraction that have
been added in Symfony 2. I hope this will fade away once I get it more,
or that it will be made a bit more transparent. The current approach
tries to make it really easy for the newbies to get into it and that is
great but if after half an hour you try to do something and get stuck
because the next step is overly complex because of it, then imo it is
not worth it.
Using the extensions is just as you said a layer for newcomers. You can
of course use the same interface as you use for Okapi. And correct me if
I'm wrong, but you cannot change the class name if the service is not
defined correctly with a parameter as the class.
Anyway I'll stop rambling because it might just be me that is too tired
to figure it out.
Keep them coming, we need all the feedback.
Thanks,
Fabien
Cheers,
Jordi
--
You received this message because you are subscribed to the Google Groups "symfony
developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en.
