Fix invalid <clear /> element in nuget.config example - #45908
Conversation
The NuGet section wrote the element as `< clear />` with a space between the angle bracket and the tag name, in the XML example and twice in the surrounding prose. XML element names cannot begin with whitespace, so the example does not parse and NuGet rejects the resulting nuget.config. The correct spelling `<clear />` is already used in "Working with the NuGet registry".
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
👋 @SurefireStudios thanks for the PR! I'll get this triaged for review. |
mchammer01
left a comment
There was a problem hiding this comment.
Nice catch! 🎯
I appreciate that you tracked down all three occurrences.
Thanks for contributing! LGTM ✅
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes:
Remove access to public registries writes the NuGet clear element as
< clear />, and XML element names cannot begin with whitespace.So the example does not parse, and NuGet rejects the
nuget.configthe article is telling readers to write.The correct
<clear />is already used twice in Working with the NuGet registry, and< clear />appears nowhere else incontent/.What's being changed (if available, include any code snippets, screenshots, or gifs):
Removed the stray space in all three occurrences — the
xmlblock plus the two prose mentions, which are wrong the same way.The block now parses:
Same article as #45907 but non-overlapping lines, so either can merge first.
Check off the following: