-
Notifications
You must be signed in to change notification settings - Fork 88
Adjusting Several Cases of Throws -> Raises #393
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
base: main
Are you sure you want to change the base?
Conversation
|
@bgribaudo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 4ea8129: ✅ Validation status: passed
For more details, please refer to the build report. |
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.
Pull request overview
This pull request continues the terminology standardization effort from PR #385, replacing instances of "throws" with "raises" to align with correct Power Query/M language terminology. In Power Query, errors are "raised" rather than "thrown" (as they would be in languages with exception handling).
Changes:
- Updated six occurrences of "throws an expression error" to "raises an error" throughout the documentation
- Updated the ms.date metadata field
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Co-authored-by: Ehren <29806264+ehrenMSFT@users.noreply.github.com>
|
Learn Build status updates of commit f5a0df6: ✅ Validation status: passed
For more details, please refer to the build report. |
Addresses https://github.com/MicrosoftDocs/query-docs/pull/385/changes#r2742705166