search

adamfoneil / Dapper.CX

A Crud library based on Dapper
MIT License
8 stars 1 forks source link

consider moving onSave delegate to ISave interface #7

Closed adamfoneil closed 4 years ago

adamfoneil commented 4 years ago

This would streamline SaveAsync a bit and better standardize the custom behavior model. Most custom behaviors (validation, get related, custom get) are interface-driven, and this one alone follows a different pattern, which doesn't feel right.

Note, I'm referring to this and this

adamfoneil commented 4 years ago

Another reason to have ISave interface is to have separate BeforeSave (sync) and AfterSave (async) actions.

adamfoneil commented 4 years ago

added a lot of interfaces to and renamed the DbSchema.Attributes project to AO.Models -- this was part of this in the form of IAudit and ITrigger