SPFx-Projekte/PortalSettings
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Activity

Aktualisiere Versionsnummer auf 3.0.4 in README.md, package.json, package-lock.json und package-solution.json. Entferne Standard-Footer aus CustomBranding und passe Tests entsprechend an.

Browse Source
This commit is contained in:
Torsten Brendgen
2026-08-18 16:19:08 +02:00
parent eef1ac7394
commit beaa3ce21d
8 changed files with 11 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/ProviderRegistry.test.ts
+2 -3
View File
@@ -36,9 +36,8 @@ assert(!!branding.storage.action, 'CustomBranding-Aktivierungsdefinition fehlt.'
assert(branding.storage.action.name === 'CustomBranding', 'CustomBranding Action-Name ist nicht stabil.');
assert(branding.storage.action.location === 'ClientSideExtension.ApplicationCustomizer', 'CustomBranding Action-Location ist ungültig.');
const defaultBranding: any = branding.createDefault(); // tslint:disable-line:no-any
assert(defaultBranding.placeholderbottom.elements.length === 1, 'Standard-Footer für CustomBranding fehlt.');
assert(defaultBranding.placeholderbottom.elements[0].children[0].attributes.href ===
'~sitecollection/SitePages/PortalSettings.aspx', 'Standard-Footer verweist nicht auf PortalSettings.');
assert(defaultBranding.placeholderbottom.elements.length === 0,
'PortalSettings darf keinen Runtime-Standard-Footer in die Konfiguration schreiben.');
const normalizedBranding: any = branding.normalize({ elements: [{ type: 'span' }], future: 7 }); // tslint:disable-line:no-any
assert(normalizedBranding.placeholdertop.elements.length === 1, 'Legacy-Branding-Elemente werden nicht übernommen.');
assert(normalizedBranding.future === 7, 'Unbekannte Branding-Properties gehen verloren.');