Update doc to clarify modern SharePoint guidance#10902
Conversation
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 |
|
Learn Build status updates of commit 26c62f7:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/general-development/user-segmentation-in-sharepoint.md | View | Details |
docs/general-development/user-segmentation-in-sharepoint.md
- Line 32, Column 144: [Warning: file-not-found - See documentation]
Invalid file link: 'previous-versions/office/developer/sharepoint-2010/ee535520(v=office.14)'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 2204718:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/general-development/user-segmentation-in-sharepoint.md | View | Details | |
| docs/solution-guidance/information-management-policy-sharepoint-add-in.md | View | Details |
docs/general-development/user-segmentation-in-sharepoint.md
- Line 32, Column 144: [Warning: file-not-found - See documentation]
Invalid file link: 'previous-versions/office/developer/sharepoint-2010/ee535520(v=office.14)'.
docs/solution-guidance/information-management-policy-sharepoint-add-in.md
- Line 38, Column 3: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/office-365-development-patterns-and-practices-solution-guidance' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 38, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/office-365-development-patterns-and-practices-solution-guidance' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
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 |
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 |
|
Learn Build status updates of commit ad1a4f5:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/general-development/user-segmentation-in-sharepoint.md | View | Details | |
| docs/solution-guidance/information-management-policy-sharepoint-add-in.md | View | Details | |
| docs/general-development/how-tos-for-sharepoint.md | ✅Succeeded | View |
docs/general-development/user-segmentation-in-sharepoint.md
- Line 32, Column 144: [Warning: file-not-found - See documentation]
Invalid file link: 'previous-versions/office/developer/sharepoint-2010/ee535520(v=office.14)'.
docs/solution-guidance/information-management-policy-sharepoint-add-in.md
- Line 38, Column 3: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/office-365-development-patterns-and-practices-solution-guidance' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 38, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/office-365-development-patterns-and-practices-solution-guidance' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
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 |
|
Learn Build status updates of commit 58bc066:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/general-development/user-segmentation-in-sharepoint.md | View | Details | |
| docs/solution-guidance/information-management-policy-sharepoint-add-in.md | View | Details | |
| docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md | 💡Suggestion | View | Details |
| docs/general-development/how-tos-for-sharepoint.md | ✅Succeeded | View |
docs/general-development/user-segmentation-in-sharepoint.md
- Line 32, Column 144: [Warning: file-not-found - See documentation]
Invalid file link: 'previous-versions/office/developer/sharepoint-2010/ee535520(v=office.14)'.
docs/solution-guidance/information-management-policy-sharepoint-add-in.md
- Line 38, Column 3: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/office-365-development-patterns-and-practices-solution-guidance' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 38, Column 3: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/office-365-development-patterns-and-practices-solution-guidance' will be broken in isolated environments. Replace with a relative link.
docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md
- Line 155, Column 27: [Suggestion: other-site-link-broken - See documentation]
Link 'https://technet.microsoft.com/library/ee806878%28v=office.15%29.aspx' points to a page that doesn't exist. Check the path or URL and update the link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
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 |
|
Learn Build status updates of commit a484f3e:
|
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 |
|
Learn Build status updates of commit 89657df:
|
Category
Related issues
-fixes SPFx Docs Update for content: docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md #10903
-fixes SPFx Docs Update for content: docs/general-development/modify-sharepoint-components-for-mds.md #10906
-fixes SPFx Docs Update for content: docs/general-development/how-to-restrict-udf-code-access-security-permissions.md #10907
What's in this Pull Request?
Updated doc