2 ms·
We already do something similar. Strong parameters is a terrible api since it splits the schema and tge "authorized parameters", which is really just the same.
by Fire-Dragon-DoL 4y ago
We already do something similar. Strong parameters is a terrible api since it splits the schema and tge "authorized parameters", which is really just the same.
Aside from that, I don't love dry libs either, they are often very complex for their usecases and they all have DSLs that could have been better served by using ruby, datastructures and objects