dry-rb/chat

WE MOVED TO ZULIP => https://dry-rb.zulipchat.com <=

Kumayl Nazary

@knazary

Got it. This was great. In relation to my local bundle cache, which file(s)/directory would be the right one to push to a repo of my own?

Tim Riley

@timriley

If it’s a git repo clone, you want to push the whole thing up

Kumayl Nazary

@knazary

Tim Riley

@timriley

¯_(ツ)_/¯

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

Nikita Shilnikov

@flash-gordon

I would check out bundler

Kumayl Nazary

@knazary

Thanks a bunch @timriley ! Will try this workaround for now. And next up will be a real upgrade.

Nikita Shilnikov

@flash-gordon

since it's a git-source dep it must be managed by bundler, not rubygems

Kumayl Nazary

@knazary

@flash-gordon could you expand/elaborate on what you mean?

Tim Riley

@timriley

Go into your (hopefully working) local checkout of the app

type bundle show rodakase

that will show you where bundler has checked out the copy of the gem

Kumayl Nazary

@knazary

probably because i'm using rbenv

ah found it.. that was cuz i removed my gemfile.lock

Nikita Shilnikov

@flash-gordon

okay then you can re-push it wherever you like and update your gemfile after that

Kumayl Nazary

@knazary

Gonna try now -- appreciate you both @flash-gordon @timriley

Marwan Rabbâa

@waghanza

I've met a hanami failure with the last dry-logic

the-benchmarker/web-frameworks#850

has anyome meet this issue ?

Nikita Shilnikov

@flash-gordon

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

Marwan Rabbâa

@waghanza

ok. course I've pined version for my benchmark

https://github.com/the-benchmarker/web-frameworks

Marwan Rabbâa

@waghanza

however, I see that hanami-validation is pined to dry-validation 0.11.x
https://github.com/hanami/validations/blob/v1.3.1/hanami-validations.gemspec#L22

Tim Riley

@timriley

https://twitter.com/dry_rb/status/1090394854645948416

Piotr Solnica

@solnic

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:

Piotr Solnica

@solnic

https://twitter.com/_solnic_/status/1090959293573197824

@pablocrivella code reloading in rails may get in your way. so be aware of that

Nikita Shilnikov

@flash-gordon

rails way vs your way

@knazary glad to hear that

Piotr Solnica

@solnic

also this https://www.reddit.com/r/ruby/comments/alpcvf/introducing_dryschema/

Pablo Crivella

@pablocrivella

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

Nikita Shilnikov

@flash-gordon

I don't think there's a general better approach, if you want to stub it once in tests then you could conditionally register items depending on the environment

I use it in both ways

Pablo Crivella

@pablocrivella

Now i’m hadling it with before and after hooks to stub and unstub, i hope it doesn’t have a big performance cost on the tests

Nikita Shilnikov

@flash-gordon

the cost is close to zero compared to what you normally do in tests

anyway, I use around and stub with passing a block

Where communities thrive

People

Repo info

Activity