NewSAPUI5 and OpenUI5
In the last 30 days
Change
  • Released0
  • Added to the atlas0
  • New content0
  • Revised3
Kind
Origin: SAP
Domain: 2
Clear all
3 changes
Origin SAPDomain UI & Frontend BridgeDomain Integration & Messaging

Sat 17
1 change
Establish a central inbox with SAP Task Centerexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Thu 15
1 change
@openui5/sap.ui.coreprovides[capability:ui5-testing] revisedThe edge carried no source, so what the package answers for this capability was an unattributed claim. The three parts are each stated by SAP's own documentation, and the level the package covers, unit and integration, is the comparison the capability now declares. End-to-end is left absent rather than entered as a no: the OPA page's restrictions are the capability's boundary and are recorded there. The other six edges were not read for this job and are unchanged.Package,
Wed 14
1 change
@ui5/webcomponentssources, description revisedThe paragraph named the three component packages and the framework, which reads as the whole of what the project publishes. Its own package table lists @ui5/webcomponents-theming, @ui5/webcomponents-localization and the SAP-icons, SAP-icons-TNT and BusinessSuiteInAppSymbols collections beside them, and the npm record for 2.27.2 resolves all of them as dependencies of the main package, so what an application installs is wider than the sentence said.Package,
The last 30 days. Older changes stay in each entry's history.