Custom resolver using lambda seems not to conform to the resolver interface.

[dry-rb]

Custom resolver using lambda seems not to conform to the resolver interface.

[AMHOL]

Thank you, the docs are quite old, I'll try to get around to updating that soon.

[yewton]

It seems the docs are not valid since 2 years ago 7f905a6 🤔

So what is the correct way to define custom resolvers?
Subclassing ::Dry::Container::Resolver ?

Or, custom resolvers are not supported anymore...?

[AMHOL]

@yewton yes, subclassing should work, or just adhering to the same interface, the old interface used to just be #call but it got updated since then

[yewton]

Thank you! I'll give it a shot.

[GustavoCaso]

@yewton Thanks so much for pointing out the outdated docs.

Could be really useful if you could share how are you using custom resolver and registry in your current project. We are evaluating if the feature is worth keeping. 😄

[yewton]

@GustavoCaso Thanks for your reply!

In fact, I don't use custom resolver/registry anymore 😓

At first I wanted to achieve something like an "automatic resolver" in my Rails project, and tried to write a custom resolver that uses Rails' autoloading feature.
But I realized that such resolving processes should not be done in runtime, but should be done at startup time with "automatic registerer", like dry-system.

So now I cannot imagine any custom resolver/registry use cases...
I suspect that they are no longer needed 😰

[flash-gordon]

See #49 (comment)