Closed Stray closed 11 years ago
Sounds good to me. Depending on how much of a priority you think it is, you might want to consider sending me a pull request, though ;)
I would be delighted - I can add the errors I want this weekend. :)
I would be delighted - I can add the errors I want this weekend. :)
Great, add away :)
Fixed by c24b1cbf9e and 4ea342ccaa
Not sure if this is broadly desirable or not, but if I could have slightly more specific errors back from the injector then I'd be able to catch them and feed something useful back to the developer.
Wanted:
InjectorAttemptedInterfaceConstructionError
Use case: user does the following -
They would then also need to provide a mapping for ISkinProcess elsewhere. Otherwise, when I do
they'll see an injector error which is perhaps less useful than the one I could provide if I could specifically catch this 'tried to instantiate an interface' error and then throw one that refers to the specific mapping and the viewProcessorMap.
My other option is to catch all InjectorErrors, parse the error message, check whether it's the one I wanted and then re-throw if not... but I'd prefer not to do that.
What do you think?