-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Introduce MapperInterface #7039
Introduce MapperInterface #7039
Conversation
src/Mapper/BaseMapper.php
Outdated
@@ -21,7 +21,7 @@ | |||
* | |||
* @author Thomas Rabaix <thomas.rabaix@sonata-project.org> | |||
*/ | |||
abstract class BaseMapper | |||
abstract class BaseMapper implements MapperInterface |
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.
Does it make sense at all to have this abstract... previously all method were abstract, and now it has none.
To me , an abstract class makes sense when it have some logic and some abstract method, but this class does not have any of that (previously or after this pr)
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 can deprecate it indeed.
0ad302c
to
262aefe
Compare
262aefe
to
23fd9fa
Compare
Subject
We're using
BaseMapper
as a typehint somewhere, which is an abstract class.Isn't better to use an interface instead ?
Changelog