-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Clarify that some interface are not meant to be implemented #31447
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.
👍 as discussed, see suggestion
here are two examples where the interface needed extending: |
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.
We could even go with must not
1905d2b
to
58410b7
Compare
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.
👍
nice! please make phpcs happy |
This make sure that apps don't implement this interfaces and gives us more liberty to add new methods to them (as long as it is compatible from an usage point of view) Signed-off-by: Carl Schwan <carl@carlschwan.eu> Co-authored-by: Vincent Petry <vincent@nextcloud.com>
96259ee
to
e495c57
Compare
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
e495c57
to
5a17415
Compare
This make sure that apps don't implement these interfaces and give us
more liberty to add new methods to them (as long as it is compatible
from a usage point of view). This just documents something we were already
doing before.
Signed-off-by: Carl Schwan carl@carlschwan.eu