Passing In-Memory Specification to Repository
I am working on my DDD know-what/how and have the following questions related to the Specification Pattern, the Repository Pattern, persistence agnosticism, and performance.
fatal: repository ‘https://github.com/Kaneva134/Display-flex.git/’ not found
fatal: repository ‘https://github.com/Kaneva134/Display-flex.git/’ not found
When I try to clone a repository I received the above error message. How to solve it?
How to avoid duplication of code related to shared entities in the repository pattern?
I’m building a repository for a large CRM schema that has a high number of relations between entities.
How to avoid duplication of code related to shared entities in the repository pattern?
I’m building a repository for a large CRM schema that has a high number of relations between entities.
How to avoid duplication of code related to shared entities in the repository pattern?
I’m building a repository for a large CRM schema that has a high number of relations between entities.
How to avoid duplication of code related to shared entities in the repository pattern?
I’m building a repository for a large CRM schema that has a high number of relations between entities.
How to avoid duplication of code related to shared entities in the repository pattern?
I’m building a repository for a large CRM schema that has a high number of relations between entities.
Generic Repositories with DI & Data Intensive Controllers
Usually, I consider a large number of parameters as an alarm bell that there may be a design problem somewhere. I am using a Generic Repository for an ASP.NET application and have a Controller with a growing number of parameters.
More appropriate to validate a dependency filter parameter by mock+stub or by expression compile?
My lead is enforcing TDD on our project. He says he’s following Uncle Bob (Robert Martin) and SOLID principles. One of the rules he’s reinforcing is what I call “the single cog rule”–there should be no more than one cog in the implemented chain in your unit test.
Is a repository return a graph of entities violating SRP?
I’m working in this scenario