-
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
why double registration if "name" is given? #9
Comments
A We could deprecate usage of the dotted path in 1.x-series and in a 2.0 release change the default of |
I would add right now a deprecation notice, if we want users to use one approach rather than the other let's be clear and open about it. It has the extra benefit of "forcing" you to fix the code and take a look at it, as well as a nice feeling of following best practices 😃 |
Oh, and this could mean that the name_only attribute could be removed all together in a new major release. Keep code clean and simple! 😃 |
And we need to change all our documentation too. |
So point is: we allow to register by name and by dotted path, it seems that there is no real benefit of having both registrations, it was just out of organic evolution, so we should decided on one method and clearly mark the other as deprecated so all code can be ported to it. Who's going to make the decision? :-) |
If the "name" attribute is given in behavior ZCML registration, the behavior is registered twice. From user perspective, the registrations appear the same. This is very confusing.
Yet this behavior of p.b. is actually mentioned in the p.b. docs which leads me to assume this is intended behavior rather than a bug.
Is this indeed intended feature, and if, for what purpose?
The text was updated successfully, but these errors were encountered: