|
|
|
|
|
|
by Berone
880 days ago
|
|
|
Heavy Ruby/Rails user here. We basically run type checking on major hand-offs between modules using DrySchema/DryValidation, a gem that makes it easy to set that up. Without doing this, the integrity of the codebase erodes with scale. |
|
|
I've had real problems upgrading client's projects built using DryValidation prior to v1 in the past.
They changed the syntax of the validations just enough to break stuff and completely removed features like shared predicates. The upgrade process was very poorly documented with suggestions to go read random blog posts.
I think the replacement for shared predicates was supported be macros but even that is marked as likely to be removed in v2.
Just looking through some of the Dry changelogs the work BREAKING still features far more than I'm happy with. I'd be much happier to use Sorbet or an RBS based typing solution than work with Dry again.
It might have advantages over ActiveModel but ActiveModel is far better supported.