On 2/8/11 9:08 AM, ryan weaver wrote:
Hey guys-
I may have just missed the easy answer - so I appreciate the help in
advance.
Most end-user bundles will have a DI resource or two and will just
import them from the main application configuration resource (without
the need for any DI extension class). This is similar to what you see
already commonly with routing.
But what is the syntax for this? The routing has a "@BundleName/..."
syntax, but that doesn't appear to be true for the DI configuration.
Currently, I'm using the following:
imports:
hello_bundle:
resource:
../../src/Sensio/HelloBundle/Resources/config/services.yml
This was not implemented... but now it should work:
imports:
hello_bundle:
resource: @SensioHelloBundle/Resources/config/services.yml
Fabien
Am I missing the better solution?
Thanks!
Ryan Weaver
Lead Programmer - iostudio - Nashville, TN
http://www.iostudio.com
http://www.thatsquality.com
Twitter: @weaverryan
--
If you want to report a vulnerability issue on symfony, please send it
to security at symfony-project.com
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
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
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
