-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add link for reserved namespace error during package upload #8610
Conversation
I recommend including the link as part of the statement, something like: ... or re-upload the package with a different ID. Click here to learn more about the Package ID prefix reservation. |
Assert.Equal(Strings.UploadPackage_IdNamespaceConflict, (result.Data as JsonValidationMessage[])[0].PlainTextMessage); | ||
Assert.Null((result.Data as JsonValidationMessage[])[0].RawHtmlMessage); | ||
Assert.Equal(Strings.UploadPackage_IdNamespaceConflictHtml, (result.Data as JsonValidationMessage[])[0].RawHtmlMessage); | ||
Assert.Null((result.Data as JsonValidationMessage[])[0].PlainTextMessage) ; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assert.Null((result.Data as JsonValidationMessage[])[0].PlainTextMessage) ; | |
Assert.Null((result.Data as JsonValidationMessage[])[0].PlainTextMessage); |
Here's an interesting perspective on using "here" for link text: https://www.smashingmagazine.com/2012/06/links-should-never-say-click-here/ |
Can we say (with the full text as link): |
Summary of the changes (in less than 80 characters):
Add link to message when there is conflict of namespace during uploading package
After changes:
Addresses #8397