Closed sdepouw closed 5 years ago
It's not the registration that gets screwed up, but the generated Expressions. I've got the fix for this done that will be in Lamar 3.0.2 either later today or at least early this week. Thank you for the repro steps here.
@sdepouw Misspoke, Lamar 3.0.3, and I'm starting the mechanics to release that right now
This may be related to #28 but I am not certain. I'm using v3.0.1 NuGet package of Lamar.
Say I have the following (based on Decorator documentation):
I have the following (NUnit) unit test:
This unit test currently fails, because the constructor of
WidgetDecorator
takes in a parameter namedwidget
, which somehow screws Lamar's registration up. If I change the parameter name to anything butwidget
(whether renaming it to something else, or just changing the casing toWidget
,wiDget
, etc.), the test passes.It appears to be related to the concrete type
Widget
's name. If the parameter name matches the concrete type name, it blows up.This is being done in part of a project of converting StructureMap over to Lamar. The original StructureMap implementation does not run into this issue (the unit test passes without issue).