The SpecificationRepository was turned into SpecificationRepositoryTrait in #19.
This is totally fine, however I know at least one implementation that still extends SpecificationRepository.
In order not to break backwards compatibility, I put back the SpecificationRepository class, but let it use the newly added SpecificationRepositoryTrait.
Coverage remained the same at 99.638% when pulling b8ee11151676d071b232880d8390b69be0928332 on add-specification-repository-class into 75cc200edbd029e043aace371ef9ac1225cff352 on master.
Coverage remained the same at 99.638% when pulling b8ee11151676d071b232880d8390b69be0928332 on add-specification-repository-class into 75cc200edbd029e043aace371ef9ac1225cff352 on master.
Coverage remained the same at 99.638% when pulling 771c5f473aa08eb11841a13c53f03648ea503200 on add-specification-repository-class into 75cc200edbd029e043aace371ef9ac1225cff352 on master.
Coverage remained the same at 99.638% when pulling 03558e086d7d36fad3b725c68421bdebc7c231e3 on add-specification-repository-class into 75cc200edbd029e043aace371ef9ac1225cff352 on master.
Coverage remained the same at 99.638% when pulling 03558e086d7d36fad3b725c68421bdebc7c231e3 on add-specification-repository-class into 75cc200edbd029e043aace371ef9ac1225cff352 on master.
The SpecificationRepository was turned into SpecificationRepositoryTrait in #19.
This is totally fine, however I know at least one implementation that still extends SpecificationRepository.
In order not to break backwards compatibility, I put back the SpecificationRepository class, but let it use the newly added SpecificationRepositoryTrait.