Update for latest dry-configurable setting API

[timriley]

No description provided.

[solnic]

I think I want to make it work with both versions until 2.0.0. Thoughts?

[timriley]

@solnic good thought, and I think you're right, particularly for the post-1.0 gems of ours. Do you have any thoughts about how to go about it?

[solnic]

@timriley I did this here 5ff1883 but also did this there 0471911aa95a184f594cfded07f762becad09489 so if we require latest dry-schema here then what I did here won't be needed

EDIT 3: fixing link to dry-schema commit 🙄

[timriley]

@solnic I like what you did over in 0471911 (dry-schema #356) — would you be happy with that approach here too?

[solnic]

@timriley yes sorry that's what I meant 🙂 the only "issue" is that we would have to ensure the new dry-validation depends on the new dry-schema too...unless you want to override setting here as well?

[timriley]

@solnic Yeah, I think we'd want to put this shim directly in every gem that uses such an approach

[solnic]

@timriley done here c8ad125

[timriley]

Thanks to the improved backwards compatibility in the upcoming dry-configurable deprecations (tested in dry-rb/dry-configurable#120), this one no longer needed any kind of additional shim.