Florian Vogt
Florian Vogt
Hi Developers, i am looking for a nice tutorial / example project where Rollup, ES6, Karma and Karma Coverage is used. I try to get the coverage reporting working. Test...
This is a draft, likely to contain more topics than we will actually be able to work on. We appreciate your feedback. ## UI5 Tooling 4.0 ### Breaking changes -...
When using version `10.0.1` it was possible to use `import $RefParser from "@apidevtools/json-schema-ref-parser";` When upgrading to `10.1.0` the default export doesn't work anymore. I have to use the named export....
JIRA: CPOUI5FOUNDATION-296 Depends on: - https://github.com/SAP/ui5-builder/pull/957 - https://github.com/SAP/ui5-server/pull/617 - https://github.com/SAP/ui5-project/pull/683
Thats an alternative for https://github.com/SAP/openui5-sample-app/pull/90. Currently, the loader config has to be overridden because for some special artefacts UI5 define mapping paths. See https://github.com/SAP/openui5/blob/17f1aed3c1bb799b7ef1adfc0f5d2f171a029e3f/src/sap.ui.core/src/ui5loader-autoconfig.js#L969.
We have configured the default CodeQL setup for our repo https://github.com/SAP/ui5-tooling-extensions/. CodeQL checks run for every PR and weekly on the default branch. However fossstars does not recognize this https://github.com/SAP/ui5-tooling-extensions/blob/fosstars-report/fosstars_report.md#how-a-project-uses-codeql.
Allows client side code coverage generation for ES6+ code powered by https://github.com/SAP/ui5-tooling-extensions/tree/main/packages/middleware-code-coverage. Projects generated for UI5 versions before 1.113.0 will stick to old "Blanket.js" based code coverage determination limited to...
Add deprecation info to README.md
Migrate default branch to 'main'. JIRA: CPOUI5FOUNDATION-574
Up until UI5 Tooling v3, the bundle option "usePredefineCalls" defaults to "false" and has to be activated explicitly in a custom bundle configuration. For default bundles, such as Component-preload or...