-
Notifications
You must be signed in to change notification settings - Fork 21
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
Adapt to changes of MemberData in CMFCore #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (I would remove the FIXME)
@implementer(IManageCapabilities) | ||
class MemberData(BaseMemberData): | ||
# FIXME: MemberData should probably be a more specific adapter | ||
# instead of a subclass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the Interface is the same, there is no need to subclass IMember just for the sake of being more specific, so IMO this is perfectly fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review. I'll remove the the FIXME.
I guess we need a legacy-branch when we merge this. Because this will not work in Plone 5.x. Merging can wait untill we have a stable 5.1 release and/or a new 6.0 branch for the coredev. |
Imo: Branch the current master as 5.x, and set it in coredev sources.cfg as the current. Increase major version number here to 6.0.dev0, in setup.py depend on CMFCore >=... and go on. |
Do not merge!
Fixes #24 for compatability with Zope 4