repository

@furystack/repository — the Repository pattern with DataSets, authorization, and event callbacks

Bye-bye extension methods

Using extension methods was fun at the beginning but I've ran into more and more problems with them

Build a business layer with a Repository

A Repository is the next layer above the data stores. When setting up a repository, you can create DataSets that can rely on a previously configured physical store. The difference is that while PhysicalStore focuses on the data, DataSet focuses on business logic. You can authorize, check permissions, subscribe to entity changes, etc...