I changed the class to look for the AdapterInterface instead of the Adapter class itself
Provide a narrative description of what you are trying to accomplish:
[ ] Are you fixing a bug?
[ ] Detail how the bug is invoked currently.
[ ] Detail the original, incorrect behavior.
[ ] Detail the new, expected behavior.
[ ] Base your feature on the master branch, and submit against that branch.
[ ] Add a regression test that demonstrates the bug, and proves the fix.
[ ] Add a CHANGELOG.md entry for the fix.
[ ] Are you creating a new feature?
[ ] Why is the new feature needed? What purpose does it serve?
[ ] How will users use the new feature?
[ ] Base your feature on the develop branch, and submit against that branch.
[ ] Add only one feature per pull request; split multiple features over multiple pull requests
[ ] Add tests for the new feature.
[ ] Add documentation for the new feature.
[ ] Add a CHANGELOG.md entry for the new feature.
[x] Is this related to quality assurance?
This change will make the class rely on the abstraction (interface) instead of the concretion (the class itself)
michalbundyra
commented
4 years ago
I changed the class to look for the AdapterInterface instead of the Adapter class itself
Provide a narrative description of what you are trying to accomplish:
[ ] Are you fixing a bug?
masterbranch, and submit against that branch.CHANGELOG.mdentry for the fix.[ ] Are you creating a new feature?
developbranch, and submit against that branch.CHANGELOG.mdentry for the new feature.[x] Is this related to quality assurance? This change will make the class rely on the abstraction (interface) instead of the concretion (the class itself)
[ ] Is this related to documentation?