Skip to content
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

Symfony autowiring broken by JMSDiExtraBundle #282

Open
Aerendir opened this issue Jun 27, 2017 · 8 comments
Open

Symfony autowiring broken by JMSDiExtraBundle #282

Aerendir opened this issue Jun 27, 2017 · 8 comments

Comments

@Aerendir
Copy link

Aerendir commented Jun 27, 2017

It seems that the bunde breaks the autowiring functionalities of Symfony, making it impossible to use them.

All the etails in the ticket opened in the Symfony's issue tracker: symfony/symfony#23200 (comment)

@Kadbury1989
Copy link

Its really a pain that this issue still exists. Is there any active development going on to fix this?

@ostrolucky
Copy link

also see symfony/symfony#27053

@schmittjoh
Copy link
Owner

I'm not sure we still need this bundle given the addition of autowiring and recent improvements to it.

Could you tell us a bit more what features you still use of this bundle that are not supported by the Symfony dependency injection container itself?

@ostrolucky
Copy link

Personally I use no features of this bundle, it's just required by jmsjobqueuebundle

@schmittjoh
Copy link
Owner

If you use the symfony4 branch, this requirement should not be there anymore.

@ostrolucky
Copy link

That's nice, but I'm hesitant to use dev branches in production. There should be a push for merging the branch and release it.

@Aerendir
Copy link
Author

I was using it only because required by JMSTranslationBundle. No other feature used.

Unfortunately I was forced to remove both to make Symfony autowiring work...

@rvanlaak
Copy link

rvanlaak commented May 3, 2018

Same here, would be great if JMSJobQueueBundle would not have a hard dependency on jms/di-extra-bundle in the case that symfony/symfony: ^3.4|^4.0 is used.

What would it take to let the symfony4 branch support symfony ^3.4|^4.0 instead of only ^4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants