-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Feature request: Run analyzers in debug mode #18791
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
Comments
@Rick-Anderson thanks for following up. @mkArtakMSFT I'm moving this to next milestone planning so that we can look at it then and decide. |
See #20709, caused by middleware in the wrong order. |
How to use Static Files with CatchAll Routing? #18038 |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
For future reference, here's an easy one to miss.
|
Here's another |
Uh oh!
There was an error while loading. Please reload this page.
Problem motivation: #18768,
app.UseSpa
was in the wrong order.Add
app.UseRunAllAnalyzers
to template code to detect middleware order and other problems.UseRunAllAnalyzers
could be updated frequently to add more checks.See https://twitter.com/davidfowl/status/1228902288627912705 where
@davidfowl
requests this.cc @javiercn
The text was updated successfully, but these errors were encountered: