-
Notifications
You must be signed in to change notification settings - Fork 51
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
Missing information in Readme.md #2
Comments
This also fixed my issue but raises another one (I think). I don't think the autoloader should use 'DoctrineExtensions' as the key. I'm also using @l3pp4rd's doctrine extensions implemented in Symfony2 by @stof. I'm still feeling my way around Symfony2 so I can't offer a pull request or clearly identify the issue. Happy to be told that I'm wrong but isn't there a chance of naming conflicts when using 'DoctrineExtensions'? |
There is a conflict as |
Yes, try to think some vendor namespace of your own, it will conflict otherwise |
I've created a separate issue for the potential autoloader conflict naming here: #3 |
Well, the first step is not about DI. It is about changing the namespace of the related library to something else. And this should be let to the owner so that he choose the name he wants to use. |
In autoload.php:
$loader->registerNamespaces(array(
...
'DoctrineExtensions' => DIR.'/../vendor/doctrine-extensions-taggable/lib',
));
and in app/config.yml:
fpn_tag:
model:
tag_class: FPN\TagBundle\Entity\Tag
tagging_class: FPN\TagBundle\Entity\Tagging
The text was updated successfully, but these errors were encountered: