adamfoneil / models Goto Github PK

Done in 1.1.25
see 4f45b95

the issue is if I have validation code at the model level that does database queries, then I'm tempted/required to add dependencies for that -- Dapper.CX, QX, or whatever. Dependencies like that muddy what model classes should do. See IValidate.ValidateAsync

There's no problem with the sync method so long as everyone understands it's not intended for database queries. Validation logic will really need to be in app layer.

In this project, I've used the word "model" to mean "entity," but now at long last I think "entity" is clearer.
So, for this issue, I'd like to rename all assets that refer to "models" as "entities" -- along with all dependent packages. These include:

• Dapper.Repository
• ModelSync (will become EntitySync)

I created a property called CustomerId in another project. This got made into an FK because it fits a naming rule that infers FKs when it's a combo of a table + identity property. I need to be able to make exceptions in this case to suppress the inferred FK. This is here the inference happens in ModelSync.

The idea here is to move interfaces (triggers, validation, get related, stamping, tenant isolation, etc) to a "business layer" object or "service" object in order to declutter model classes, allow simpler reuse (avoiding linked source stuff I do today to segregate IDbConnection methods), and provide an extension point for advanced functionality like concurrency and change tracking.

without the Dapper dependency of course, just the SQL creation stuff, because this is now in this package. I think should be based on IDictionary<string, object>

One annoyance I've had with Dapper.CX is that the generated crud SQL statements have a big uneven left indent because of how I use verbatim strings. I could remove the verbatim string (and craft the indents manually), but I don't want to. I'd like to have an Unindent method that left justifies multi-line strings like this