Publish standard #27795
Merged
Publish standard #27795
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributes to dotnet#27789 Change the published spec from the Microsoft C# 6 draft to the ECMA C# 6 draft.
First commit of link updates. This doesn't update all anchors.
The standard contains clause numbers, which changes the anchor text for all anchor links. Update those.
BillWagner
requested review from
KathleenDollard,
tdykstra and
a team
as code owners
Adding the C# standard created duplicate H1s. Fix this one.
IEvangelist
approved these changes
Jan 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Publish the C# Standard from the dotnet/csharpstandard repo, instead of the dotnet/csharplang repo.
Contributes to #27789
The first commit makes the necessary changes to docfx,json, openpublishing config, and the TOC.
Later commits all address links to the standard.
Note that the published location of the spec hasn't changed, so no redirections are needed.
Suggestions for reviewers:
I'd review the first commit, and look at the new spec on the review site. The other changes were found using the build report.
Internal review site