David Baldwin

If an example is of any use it appears that the `cloak_ecto` package just added support for ecto 3.5 in this PR... https://github.com/danielberkompas/cloak_ecto/pull/13 It is my assumption newer applications are...

@ClementineOldfield I'm personally thinking of waiting another couple weeks and then figuring out how to proceed. I've got a little bit of time before I have to upgrade, but don't...

@germsvel I rather like that `build` doesn't know or care about Ecto. However, one thing I have missed in ExMachina that ruby's FactoryBot (and Thoughtbot's) has is something similar to...

Here is a very limited and opinionated build_stubbed strategy I've been using... https://gist.github.com/baldwindavid/780449125ac4e9d064662895a0d65703 It does the following: - Adds `inserted_at` and `updated_at` timestamps to all records in the tree if...

Oh, that's great. I hope to see that talk once it's released!

Thanks for thinking this through. A few notes: I like the terseness of just using a list for a chain of specs. However, given that norm already matches on tuples...

After posting the above, I noticed the "Context" link in the description above. haha Based upon that, it appears that the intent is, in fact, to supplement changesets. That's great....

@kieraneglin - Thanks for the message. You're right that it is flexible enough that one can choose to break these into separate specs outside of `chained` if they really want...

@kieraneglin Yep, I really like the addition of the validation message per `spec`. But the more I think about it, I'm really wondering if that could be its own PR...

> how about a drop down for all possible vim modes Thanks for the work on this. I'd maybe lean the other way here and don't really think it's necessary...