Stephen Haberman

The initial attempt to "convert enums to classes" looks like the approach is a dead end, just because enums as so ingrained in idiomatic TS code like keys-of-records and switches,...

I guess I'm not sure what to do about `afterValidation`--I'd like to remove it, but without it there is not a differentiation between: * An `onSave` hook that helps put...

Hrm, yeah, that's interesting; I'd forgot / didn't realize that RoR runs `after_validation` before the rest ... which I guess implies the entities _must_ be valid to get to the...

> If we're moving away from the rails naming, why would we move to their naming for this? Ah yeah, I didn't mean to pick save as their terminology, it...

I kinda wonder if `beforeFlush` would, to a new user, insinuate that it is called immediately before the SQL is put on the wire (which is what "flush" means to...

Other misc thoughts: Per the brainstorming about "complete-ness of the entity" as a purpose/categorization of hooks, nearly all of our hooks are for creating side-effects within the domain model itself,...

I wonder if we could use field-level reactivity hints to replace the notion of "before create" / "before update". Like maybe there is just "before save", and something about the...

If we add a `setDefaults` hook, ideally factories would call that first before they apply their "dumb" defaults.

Yeah, that's a good point, we could add a before/after validation that specifically see maybe-invalid entities, and then hopefully by the time before/after create/save are called, the entity is ensured...

Async derived fields have the same issue: ``` config.setAsyncDerivedField( "identifier", { identifier: {}, commitment: { changeOrders_ro: "identifier_ro" } }, (changeOrder) => { const commitment = changeOrder.commitment.get; // Maybe we could...