Skip to content

Update iclientsidecomponentmanifest.yml #73

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 10, 2024
Merged

Update iclientsidecomponentmanifest.yml #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions SP-Framework/sp-module-interfaces/iclientsidecomponentmanifest.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,8 +103,10 @@ properties:
package: '@microsoft/sp-module-interfaces!'
fullName: requiresCustomScript
summary: >-
If true, the component can only be installed on sites where Custom Script is enabled. This should be set to true
if the component allows authors to execute arbitrary scripts on the page.
If true, the component behaves as following on sites where custom scripts are not allowed to run:
- when the component is a web part, it is not available in the web part picker
- every instance of the component that was added to the page while custom scripts were allowed to run, will no longer surface in those pages. Author are still able to remove those components while editing the page

remarks: >-
Defaults to false. See
https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f
Expand Down