yes, you can pin it to ~> 0.4.2, we also released dry-validation 0.12.3 which has this dependency, unfortunately, I'm afraid hanami depends on an older version of dry-validation
hey folks, I've finally finished first version of dry-schema and it was pushed to rubygems today. Rough docs are here https://dry-rb.org/gems/dry-schema/ (heavily based on current dry-validation docs). Feel free to test it out and let me know how it goes. I'll be publishing a blog post about this release later this week or after Feb 11. Anyhow, check out the docs, gem i dry-schema and have fun. This also means that I'll start working on dry-validation 1.0.0 in February.
Vasily Kolesnikov
@v-kolesnikov
:tada:
I'll test it soon.
Piotr Solnica
@solnic
btw it is possible to have both dry-validation and schema installed (FWIW)
Christopher Swasey
@endash
Good timing. I was just looking at both this week and was confused that -schema didn't seen to exist yet.
Pablo Crivella
@pablocrivella
Question: On a rails app, would it be recommended to define my DI Container on an initializer?Currently i don't have it there, but idk if there could be some issues with that
Piotr Solnica
@solnic
@pablocrivella yes this should work well, I've done that in the past and had no problems with such a setup
Pablo Crivella
@pablocrivella
I was having some issues when combined with dry-auto_inject tho
That were fixed by moving the Container to an initializer, but maybe the issue was something else?
Kumayl Nazary
@knazary
@timriley@flash-gordon just wanted to thank you both for your workaround suggestions from the other day. Finding the checked out copy of the missing commits in my local bundle cache and pushing to a repo of my own did the job :pray:
What would be a better approach when using dry-container for testing? Should i stub and unstub per example? or stub everything and unstub where needed? I couldn’t find an unstub_all method