We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would be nice to use model classes which implement a BuyableInterface instead of relying on concrete classes and mapped attributes.
BuyableInterface
interface BuyableInterface { function getBuyableId(); function getBuyableName(); .... }
A BuyableRepository which implements a BuyableRepositoryInterface will be used to retrive items from any kind of storage system.
BuyableRepository
BuyableRepositoryInterface
interface BuyableRepositoryInterface { function findByBuyableId(); .... }
The text was updated successfully, but these errors were encountered:
Agree 100%. Ill try to get to it this weekend. Also 2.0 is around the corner hoping soon but cant say a timeline for sure.
Sorry, something went wrong.
I can help if you want, maybe I can do it even today if we can define interfaces' methods.
That would be awesome! Im more than happy to accept a PR.
No branches or pull requests
Would be nice to use model classes which implement a
BuyableInterface
instead of relying on concrete classes and mapped attributes.A
BuyableRepository
which implements aBuyableRepositoryInterface
will be used to retrive items from any kind of storage system.The text was updated successfully, but these errors were encountered: