Just find a working local cached copy, if you can, push it up, then point your Gemfile to that repo’s master
I have no idea if this will work, but it’s something
It’s late here and I don’t have the time to look into bundler’s internals right now so unfortunately I can’t help further
type
bundle show rodakase
that will show you where bundler has checked out the copy of the gem
ah found it.. that was cuz i removed my gemfile.lock
I've met a
hanami failure with the last dry-logic
has anyome meet this issue ?
however, I see that
https://github.com/hanami/validations/blob/v1.3.1/hanami-validations.gemspec#L22
hanami-validation is pined to dry-validation 0.11.xhttps://github.com/hanami/validations/blob/v1.3.1/hanami-validations.gemspec#L22
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.
I'll test it soon.
That were fixed by moving the Container to an initializer, but maybe the issue was something else?
@pablocrivella code reloading in rails may get in your way. so be aware of that
@knazary glad to hear that
I use it in both ways
anyway, I use
around and stub with passing a block
like
around { |ex| container.stub('foo123', Object.new, &ex) }