-
Notifications
You must be signed in to change notification settings - Fork 837
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
[Outlook] (spam reporting) Add support for the unified manifest for Microsoft 365 #940
base: main
Are you sure you want to change the base?
[Outlook] (spam reporting) Add support for the unified manifest for Microsoft 365 #940
Conversation
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.
One change and some questions.
|
||
1. Follow the steps in [Try it out](#try-it-out) to test the sample. | ||
|
||
> **Note**: You can't debug a spam-reporting add-in that uses the unified manifest at this time. |
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.
Just for my personal curiosity, why would this be? The JavaScript that's being debugged is the same, isn't it? Why would the type of manifest matter?
1. Download the **outlook-spam-reporting.zip** file from this sample to a folder on your computer. | ||
1. Sideload the sample to Outlook by following the instructions in [Sideload with the Teams Toolkit CLI (command-line interface)](https://learn.microsoft.com/office/dev/add-ins/testing/sideload-add-in-with-unified-manifest#sideload-with-the-teams-toolkit-cli-command-line-interface). | ||
1. Follow the steps in [Try it out](#try-it-out) to test the sample. | ||
|
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.
Should we tell readers how to stop and uninstall with teamsapp uninstall
? In the localhost section, we tell them how to stop.
1. Download the **manifest.xml** file from this sample to a folder on your computer. | ||
1. Sideload the add-in only manifest in Outlook on the web or on Windows (new or classic) by following the manual instructions in [Sideload Outlook add-ins for testing](https://learn.microsoft.com/office/dev/add-ins/outlook/sideload-outlook-add-ins-for-testing#sideload-manually). | ||
1. Follow the steps in [Try it out](#try-it-out) to test the sample. | ||
|
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.
Should we tell readers how to stop and uninstall?
{ | ||
"id": "onSpamReport", | ||
"type": "executeFunction", | ||
"displayName": "onSpamReport", |
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.
"actions.displayName" is only used in add-ins that have keyboard shortcuts. If this add-in doesn't let's remove this property.
What's in this Pull Request?
Adds support for the unified manifest for Microsoft 365 to the spam-reporting sample.