3 ms·
That's actually a case of a bad error message. It just means it can't find 'Foo'. The DI looks for 'Foo', can't find it so it looks for 'FooProvider', can't f
by wmil 12y ago
That's actually a case of a bad error message. It just means it can't find 'Foo'.
The DI looks for 'Foo', can't find it so it looks for 'FooProvider', can't find it, and throws an error saying it can't find 'FooProvider'.
- serve_yay 12y agoI just think that's a bad way for it to work. It should look for the thing by the name you give it and then find that thing, or not. edit: This portion of a down thread comment captures my complaint well: "In a sane framework, errors are meant to direct you to the cause, not simply to announce that something somewhere is written in a way that the framework doesn't like because of complex reason foo."