Virtus gem not actively maintained about valkyrie HOT 3 CLOSED

So the "replacement" for Virtus is dry-struct: https://github.com/dry-rb/dry-struct , which is a core dependency of ROM https://github.com/rom-rb/rom . I've never been able to get ROM to work, and I have some level of concern about the scope of ROM being way bigger than the scope of Valkyrie.

Regarding dry-struct - I think we can make it work, but there's one big difference: dry-structs are immutable. They have no setters. The way you handle this is to have an abstraction for doing immutable actions on an existing struct - in ROM this is basically what a "repository" is, from my understanding. I'm not against that, but it makes me wonder if we're losing anything from the OO side of things.

In any case, I'd be totally open to an experiment where we rip out Virtus and make all the tests pass via dry-struct, to see what kind of interface changes we'd need and how complex our controllers would become.

from valkyrie.

The other alternative is just using our own POROs which are powered by http://trailblazer.to/gems/disposable/api.html for enabling dry-types coercion.

from valkyrie.

One way to do this is in #59 .

from valkyrie.