Tim Riley
Tim Riley
> It would be great to expose `Settings` object via `#settings` method, rather than this set object which is just some legacy we have (@timriley do you remember why it's...
BTW, @skinnyjames, regarding your original comments in the PR description: > I'm curious if this is the desired api, or if it would be easier to copy settings from another...
Thanks @skinnyjames — just left you a couple more notes in the previous batch of comments. I'll take a look at the failing specs in the next day or two,...
Related to this would be changing the expected signature for setting value processor blocks: they must be prepared for their value argument _not_ to be provided for undefined values, so...
This feature seems like the kind of generic functionality that would fit just fine in dry-container. After all, dry-container already supports the idea of "namespaces" when it comes to registering...
True, but I think that's something we can live with.
Without digging into our chat history (which I’m willing to try at some point if it will help), I’m pretty sure what @flash-gordon mentioned was right: that we followed what...
FWIW I’d be happy to consider changing the behavior if that’s the only way forward. In doing that, however, I think we should probably survey a full range of use...
Bless that person for writing such a descriptive commit message!
No update on this front, @jacobtani, nor any immediate plans AFAIK. You can be sure that we'll update or close this issue when we've done any related work.