NewSAPUI5 and OpenUI5
In the last 30 days
17 changes
Mon 19
@ui5/linteradded to the atlasStatic analysis tool for UI5 projectsLinting
@ui5/middleware-code-coverageadded to the atlasUI5 CLI middleware for Istanbul code coverageUI5 testing
@ui5/sample-appadded to the atlasOpenUI5 sample app set up with the UI5 CLI
@ui5/tooling-webcadded to the atlasDeprecated UI5 Tooling extensions for UI5 Web Components wrappersBuild and dev-server tooling
Show 3 more
UI5 Views, Reimagined: Type-Safe TSX for a Modern Dev ExperiencepublishedA Devtoberfest 2026 session on @ui5-community/jsx-runtime@ui5-community/jsx-runtimeA plugin-based JSX runtime for UI5: views are written as .tsx files with per-control typing, and the JSX compiles to plain new Control(settings) calls.community org, ui5, the incubation project that lets a UI5 view be written as TSX: XML-like markup that the TypeScript compiler checks against the control's own types and a Babel plugin turns into the constructor calls UI5 already makes. The edge to the runtime rests on the session's own description, which gives the project's documentation site as the session's documentation. The TypeScript supportTypeScript supportWriting apps and libraries in TypeScript — the type definitions, the module syntax the loader expects, and the build step that gets from one to the other.SAP and community, narrow by design edge holds because that is the session's subject — per-property checking, completion on every attribute, renames that carry through a view, and typed event objects that remove the casts — alongside what stays unchanged: string and expression bindings, controllers, routing and i18n, and XML views living beside TSX ones in the same app. The build edge rests on the setup, where ui5-tooling-transpileui5-tooling-transpileA UI5 CLI extension that transpiles modern JavaScript or TypeScript during the UI5 build, with a transformJSX option that handles JSX and TSX in the same step.community org, ui5 is given the JSX transform in ui5.yaml; the walkthrough then builds a bookshop app on a CAP OData service and names what is still missing, UI flexibility and native HTML among it.TypeScript support
vscode-ui5-language-assistantadded to the atlasVS Code extension for SAPUI5 and OpenUI5 XML views and manifestEditor support
UI5 Views, Reimagined: Type-Safe TSX for a Modern Dev Experienceexplains, summary and sources revisedThe session is about the runtime the atlas holds, and the entry named it only as "the incubation project". Its own description gives the project's documentation site as the session's documentation, "Documentation: https://ui5-community.github.io/jsx-runtime/", which is the
docs address of artifact:ui5-community-jsx-runtime, and that page carries the same label the session uses for the project, Incubation. The description sentence is added as a source and the summary names and links the runtime instead of pointing at it. The two edges already recorded are unchanged, and so are the claims about what the session shows: the quotes behind them were re-read on 2026-10-19. The session's own repository, github.com/petermuessig/devtoberfest2026-jsxruntime, is named in the same description and is not in the graph, so it is not an edge here.TypeScript supportSun 18
SAP Developers MCPadded to the atlasHosted MCP server of developers.sap.com tutorials and missionsAgent guidance
SAP Developers MCPentry revisedNEIGHBOURS §5.1 named the hosted MCP as a companion to index as an artifact, and the graph had no entry for it. ecosystem: umbrella because its content covers SAP technologies across stacks (llms.txt names ABAP Cloud, CAP, Fiori, HANA Cloud and integration) and no single door holds it. No read_only: the anonymous mounts are read-only, but the signed-in tier writes progress (complete_step). No tool_count: the quickstart and the API page list different tools per mount. The site also serves a GraphQL API, not recorded as an interface here for want of a page read. /mcp/homepage is left out of the description: the quickstart lists it as anonymous and the API page as signed-in.Agent guidance
Sat 17
SAP-samples/digital-manufacturing-extension-samplesadded to the atlasSamples for the six extension types of SAP Digital Manufacturing
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).Task and approval UIs
Thu 15
@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.Routing and navigation
SAP/ui-theme-designer-plugins-for-coding-agentsprovides, description revisedThe plugin's own README read on 2026-10-15 lists parameter inheritance beside component consumption in the design-tokens skill, and the entry said nothing about how the plugin gets in front of an agent. Both are facts a reader needs before the parameter mapping is any use to them.Agent guidance
UI5/plugins-coding-agentsprovides, description revisedThe old sentence named one marketplace and pointed at an installation guide without saying what it contains. The plugin READMEs read on 2026-10-15 state three routes, including a Copilot marketplace the entry did not mention, and state that the skills-only route leaves the UI5 MCP server to be installed by hand. That last fact changes what a reader gets, since the entry's own warning already turns on which server reads the project.Agent guidance
Wed 14
@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.Web Components interopTue 29
sap-fiori-guidelinesadded to the atlasAgent skill built from the Fiori Design GuidelinesAgent guidance
sap-fiori-guidelinesentry revisedRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact because the registry keeps other people's code in their own repositories. This skill is SAP's own code in that repository, so it is entered from its SKILL.md, README and references directory, as plugins/aicore-skills was on 2026-09-25. Hard rule 7: skills are indexed, never authored here.Agent guidance