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

Revert "Use existing MVC object result executor instead of Minimal API-based one" #183

Closed
wants to merge 1 commit into from
Closed

Revert "Use existing MVC object result executor instead of Minimal API-based one" #183

wants to merge 1 commit into from

Conversation

TimothyMakkison
Copy link
Contributor

Resolving #182 by reverting commit 1857120.
ProblemDetails does not resolve ObjectResultExecutor in .Net 6 as it doesn't have the required dependencies that are normally added in traditional controller setups.

@khellang
Copy link
Owner

This will just bring back #180. I have an idea on how to fix this, but I need some time. In the meantime, you can just revert back to v6.5.0, which uses the MinimalApiResultExecutor.

@TimothyMakkison
Copy link
Contributor Author

Sorry didn't see #180, would it be worth temporarily updating the sample to prevent #182?

I'll close the pull request, good luck solving it.

@TimothyMakkison TimothyMakkison deleted the fix_error_resolving_ObjectResultExecutor branch August 31, 2022 09:05
@blogcraft
Copy link

v6.5.1 is still bad with minmal api?

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

Successfully merging this pull request may close these issues.

3 participants