-
Notifications
You must be signed in to change notification settings - Fork 55
[all hosts] (Troubleshooting) Add TypeScript version number #807
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
Conversation
|
Learn Build status updates of commit be2b50f: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
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 PR adds TypeScript version information to the Office Scripts documentation to help users understand which TypeScript features are supported. This addresses a customer request in issue #806.
- Added a NOTE section specifying that Office Scripts uses TypeScript version 4.0.3
- Updated the document modification date to reflect the current change
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
|
Learn Build status updates of commit 2497c73: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
AlexJerabek
left a comment
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.
Approving, but curious why this is a note instead of a section. I don't have an opinion either way - just looking to understand.
|
@AlexJerabek My take is that the version is slightly different from the rest of the items in the article—it's more generic than the restrictions—but it still fits best into this article. I did waffle about whether it should be a section or a note though, so I'm absolutely open to making it a section if you lean that direction. |
That's fair. Please publish as is. |
Addressing customer request in #806