Skip to content

Conversation

@HowardWolosky
Copy link
Contributor

Description

Doing some clarifying wording in the friendly error message that we add to a 404 to indicate that they could be getting the error because the item truly doesn't exist, not simply due to authentication issues.

Issues Fixed

Came up due to confusion in #354

Checklist

  • You actually ran the code that you just wrote, especially if you did just "one last quick change".
  • Comment-based help added/updated, including examples.
  • Static analysis is reporting back clean.
  • New/changed code adheres to our coding guidelines.
  • Formatters were created for any new types being added.
  • New/changed code continues to support the pipeline.
  • Changes to the manifest file follow the manifest guidance.
  • Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.
  • Relevant usage examples have been added/updated in USAGE.md.
  • If desired, ensure your name is added to our Contributors list

Doing some clarifying wording in the friendly error message that we
add to a 404 to indicate that they could be getting the error because
the item truly doesn't exist, not simply due to authentication issues.
@HowardWolosky HowardWolosky added the enhancement An issue or pull request introducing new functionality to the project. label Jul 26, 2022
@HowardWolosky HowardWolosky merged commit 1466f16 into microsoft:master Dec 15, 2022
@HowardWolosky HowardWolosky deleted the 404ErrorMessage branch December 15, 2022 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement An issue or pull request introducing new functionality to the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant