Everything in UI5
Type: 2
Domain
Origin
Signals
More
Group by: Capability
Where it runs
Distributed through
Installs into
VS Code extension to serve, proxy, build and deploy UI5 projects
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
SAPUI5 extension for Visual Studio Code
Its README assumes a `manifest.json` with an app ID, JavaScript files that start with `sap.ui.define`, and access to ui5.sap.com to preload the standard library metadata. It says of TypeScript that ts-morph, its parser there, has drawbacks, and that not all linters work for TypeScript.
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
VS Code extension generating OData mock data from service metadata
VS Code side bar view of the SAPUI5 and OpenUI5 API reference
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.