Skip to content

Conversation

darrenkopp
Copy link

Summary

The documentation for the DayOfWeek enumeration currently has a bit of a weird order. It's not based on the underlying value, nor is it based on common order of days as it would appear on a calendar, nor is it alphabetical.

I believe the changes in this pull request will put the values in the order Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday. Not sure if that's controversial or not, but an alternate could be done with the week starting on Monday.

Put the members in a more sensible order that both reflects the raw value order as well as match at last one common calendaring system (it could start with Monday though)
@darrenkopp darrenkopp requested a review from a team as a code owner May 13, 2021 17:53
@ghost ghost added the area-System.Runtime label May 13, 2021
@dnfadmin
Copy link

dnfadmin commented May 13, 2021

CLA assistant check
All CLA requirements met.

@opbld33
Copy link

opbld33 commented May 13, 2021

Docs Build status updates of commit 68acb4f:

✅ Validation status: passed

File Status Preview URL Details
xml/System/DayOfWeek.xml ✅Succeeded View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

@BillWagner
Copy link
Member

ping @gewarren @joelmartinez

This change looks good, but I want to know if it will be overridden by the mdoc build in future releases.

@gewarren
Copy link
Contributor

Unfortunately this will get overwritten the next time we update the APIs, so I'll have to close this PR. So, the same fate as #4558. We do have an internal work item tracking a feature that would let customers sort enum fields either by value or alphabetically.

@gewarren
Copy link
Contributor

This has been fixed!

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

Successfully merging this pull request may close these issues.

6 participants