Sort the list w.r.t Error codes

[satishc2437]

Kindly sort the list using error code value instead of name. Its much more helpful as the error codes are grouped like 2xx, 4xx, 5xx. Folks tend to search the field name in corresponding groups.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: eb248735-9083-2ac6-00b0-9b2a3dbe7e4c
• Version Independent ID: 93fd43ba-a3ba-c9c9-7370-09d4b3d3467a
• Content: HttpStatusCode Enum (System.Net)
• Content Source: xml/System.Net/HttpStatusCode.xml
• Product: dotnet-api
• GitHub Login: @karelz
• Microsoft Alias: ncldev

[karelz]

I think that is reasonable. @mairaw anything against such change?
@satishc2437 would you be willing to put up a PR?

[mairaw]

This would have to be discussed with the engineering team @karelz since this part is auto-generated and it currently sorts field names alphabetically. I'll port to the Microsoftdocs/feedback repo for discussion.

[mairaw]

And this would impact all enumeration types, not just this one.

[mairaw]

I found this from a while back and we decided against changing the sorting order:
MicrosoftDocs/feedback#351

So I'll be closing this.

[satishc2437]

@mairaw Can you please re-open this issue and not close is as won't fix. The link that you mentioned for duplicate is not correct. These two issues are worlds apart.

Let's not use engineering constraints to degrade customer experiences. Below are some popular documentations on HttpStatusCode and all sort on values -
https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Are you saying, we should make it hard for the user to find the correct status code, not align with popular pattern used in this area, just because we have auto-generated documentation?

[mairaw]

I can reopen this but yes it's the same issue. The only way to fix this would be to add remarks that would list the error codes in order duplicating the enum field list. But the list under https://docs.microsoft.com/en-us/dotnet/api/system.net.httpstatuscode?view=netframework-4.7.2#fields is auto-generated and it was the point of discussion on the bug I posted. And that we decided not to change.