Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Docs for MvcOptions.RespectBrowserAcceptHeader don't render / media type correctly.

See original GitHub issue

The source code for MvcOptions.RespectBrowserAcceptHeader mentions the */* media type as shown by the red arrow below:

…however the */* media type ends up rendering as a forward slash / on the live docs as shown by the red arrow below:

I believe this is caused by converting the XML doc comments to markdown before converting to HTML for the live docs. The reason I think markdown is to blame is because even in this github window if you type */* without enclosing it in back quotes, it renders just the forward slash in italicized form which is hard to spot. Using Chrome DevTools, you can see the HTML doing the same via the em tag:

I suppose the fix is to use back quotes in the XML doc comments so we get proper rendering when markdown is used, but I am not sure what ramifications the back quotes will have in other contexts (e.g. when rendering in the IDE help tooltips).

Issue Analytics

State:
Created 3 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

gewarrencommented, Jan 7, 2021

Yes, that is probably a better choice than the backtick.

1reaction

mkArtakMSFTcommented, Jan 7, 2021

@gewarren can we use <c>*/*</c> instead? Will this work? Asking, because that’s something we already use in some places.

Top Results From Across the Web

MvcOptions.RespectBrowserAcceptHeader Property

Gets or sets the flag which causes content negotiation to ignore Accept header when it contains the media type /. false by default....

Asp.Net Core Action Results Explained - Hamid Mosalla

This post explains in detail how Asp.Net Core action results works, what each one of them does and when and why to use...

Modern API Design with ASP.NET Core 2

Ok, Json, File, or Content for APIs and View for rendering HTML. When working with content negotiation, it is better to use non–type...

Mastering ABP Framework

documentation to implement that architecture properly and automate the details ... C# model class. abp-form-content is where the form elements are rendered.