Everything in UI5
Type
Domain
Origin
Signals
More: MIT
Group by: Capability
UI5 library collecting an app's JavaScript errors
Release and repository quiet for 43 months.
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
UI5 Tooling middleware proxying destinations and neo-app.json routes
Quiet Release and repository quiet for 75 months.
Functional boundary It supports Basic Authentication only, so a backend that needs another method is not reachable through it.
UI5 server middleware proxying route prefixes to a backend
Release and repository quiet for 37 months.
UI5 Tooling v4 extension that registers other extensions
UI5 builder task preparing build output for the cachebuster
Release and repository quiet for 66 months.
UI5 builder task generating d.ts type declarations
UI5 builder task minifying HTML, CSS and JSON files
UI5 builder task transpiling ES6 to ES5 with Babel
Release and repository quiet for 51 months.
Babel transformer from modern ES or TypeScript to UI5 module syntax
UI5 builder task generating d.ts type declarations
Jest environment running UI5 unit tests in Node.js
UI5 MockServer extension generating mock data with Faker.js
Vitest environment running UI5 unit tests in Node.js
WebdriverIO service running QUnit test pages
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
Thirteen custom UI5 controls for abap2UI5 apps
Needs Standard ABAP 7.50 or higher, and an abap2UI5 whose frontend reserves the resourceRoot `z2ui5_cci`: a frontend predating that rename reserves `z2ui5ccc` and cannot resolve the controls. Frontend artefacts only one company needs, such as an in-house reuse library, a corporate icon font or company CSS, are what [abap2UI5-addons/custom-controls-customer](https://github.com/abap2UI5-addons/custom-controls-customer) is for, the same mechanism under the second reserved root `z2ui5_ccc`. ExportSpreadsheet needs SAPUI5: under OpenUI5 `sap.ui.export` is missing and the button renders disabled.
UI5 custom control rendering a PDF from a base64 data URI
Quiet Release and repository quiet for 41 months.
Functional boundary The case it is written for is a document that has not been uploaded; anything already served from a URL is what the framework's own PDF control takes. Passing a document as a data URI means holding it in the page as a string first, which is a different cost from streaming it from a server.
OpenUI5 JSONModel extension with CRUD over HTTP
OpenUI5 library validating view fields against JSON schema
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
CLI translating UI5 i18n.properties files with OpenAI
