Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest version causes a fixture error #181

Open
sahar2550 opened this issue Sep 12, 2022 · 1 comment
Open

Latest version causes a fixture error #181

sahar2550 opened this issue Sep 12, 2022 · 1 comment

Comments

@sahar2550
Copy link

I used Scrutor for decoration in an Asp.net core application and it worked fine with version 4.1.0. But after updating to 4.2.0, it causes some tests to fail.

container.TryDecorate<IX, X>();
            container.AddCors(options =>
                {
                    options.AddPolicy(name: Constants.X, builder => {
                        builder.AllowAnyOrigin()
                               .AllowAnyHeader()
                               .AllowAnyMethod()
                               .Build();
                    });
                });
Message: 
System.AggregateException : One or more errors occurred. (The method or operation is not implemented.) (The following constructor parameters did not have matching fixture data: xFixture fixture)
---- System.NotImplementedException : The method or operation is not implemented.
---- The following constructor parameters did not have matching fixture data: xFixture fixture

Any idea how that might happen? It works with downgrading.

@khellang
Copy link
Owner

khellang commented Sep 13, 2022

Hey @sahar2550! 👋🏻

It's probably related to the DecoratedType introduced in 4.2.0.

I'm not sure how the attached code is related to the xFixture error message though 🤔 Do you have a complete repro?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants