From 4f480cf41729035372973ce5dfafdce718383ab2 Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Tue, 12 May 2026 12:45:37 +0200 Subject: [PATCH 1/6] fix: broken links detected with new blc --- guides/deploy/to-kyma.md | 2 +- guides/integration/calesi.md | 2 +- java/reflection-api.md | 2 +- node.js/cds-i18n.md | 4 ++-- node.js/cds-test.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/guides/deploy/to-kyma.md b/guides/deploy/to-kyma.md index f083c470d8..b36796a979 100644 --- a/guides/deploy/to-kyma.md +++ b/guides/deploy/to-kyma.md @@ -671,6 +671,6 @@ Cloud Native Buildpacks provide advantages like embracing [best practices](https Additionally Cloud Native Buildpacks can be easily plugged together to fulfill more complex requirements. For example the [ca-certificates](https://github.com/paketo-buildpacks/ca-certificates) enables adding additional certificates to the system trust-store at build and runtime. When using Cloud Native Buildpacks you can continuously benefit from best practices coming from the community without any changes required. -[Learn more about Cloud Native Buildpacks Concepts.](https://buildpacks.io/docs/concepts/){ .learn-more} +[Learn more about Cloud Native Buildpacks Concepts.](https://buildpacks.io/docs/for-platform-operators/concepts/){ .learn-more}
diff --git a/guides/integration/calesi.md b/guides/integration/calesi.md index 7c26d0575f..1a6669341f 100644 --- a/guides/integration/calesi.md +++ b/guides/integration/calesi.md @@ -376,7 +376,7 @@ This would add this to the generated output: ### Publishing APIs -The output of `cds export` is a valid _npm_ or _Maven_ package, which can be published to any npm-compatible registry, such as the public [*npmjs.com*](https://www.npmjs.com/) registry, or private registries like [*GitHub Packages*](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry), [*Azure Artifacts*](https://learn.microsoft.com/en-us/azure/devops/artifacts/npm/npm-overview?view=azure-devops), or [*JFrog Artifactory*](https://jfrog.com/confluence/display/JFROG/NPM+Registry). For example: +The output of `cds export` is a valid _npm_ or _Maven_ package, which can be published to any npm-compatible registry, such as the public [*npmjs.com*](https://www.npmjs.com/) registry, or private registries like [*GitHub Packages*](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry), [*Azure Artifacts*](https://learn.microsoft.com/en-us/azure/devops/artifacts/npm/npmrc), or [*JFrog Artifactory*](https://jfrog.com/confluence/display/JFROG/NPM+Registry). For example: ```shell npm publish ./apis/data-service diff --git a/java/reflection-api.md b/java/reflection-api.md index e23962609f..b88fe1b6de 100644 --- a/java/reflection-api.md +++ b/java/reflection-api.md @@ -222,7 +222,7 @@ The active feature set can't be changed within an active transaction. ### Toggling SAP Fiori UI Elements -In an [SAP Fiori elements](https://experience.sap.com/fiori-design-web/smart-templates/) application, the UI is captured with annotations in the CDS model. Hence, toggling of [SAP Fiori elements annotations](../guides/uis/fiori#what-are-sap-fiori-annotations) is already leveraged by the above concept: To enable toggling of such annotations (and thus UI elements), it's required that the EDMX returned by the `$metadata` respects the feature vector. This is automatically achieved by maintaining different model variants according to activated features as described in the previous section. +In an [SAP Fiori elements](https://www.sap.com/design-system/fiori-design-web/v1-145/discover/frameworks/sap-fiori-elements/smart-templates) application, the UI is captured with annotations in the CDS model. Hence, toggling of [SAP Fiori elements annotations](../guides/uis/fiori#what-are-sap-fiori-annotations) is already leveraged by the above concept: To enable toggling of such annotations (and thus UI elements), it's required that the EDMX returned by the `$metadata` respects the feature vector. This is automatically achieved by maintaining different model variants according to activated features as described in the previous section. ### Features on the Database diff --git a/node.js/cds-i18n.md b/node.js/cds-i18n.md index 3d1f8e0845..619e3f1cce 100644 --- a/node.js/cds-i18n.md +++ b/node.js/cds-i18n.md @@ -97,7 +97,7 @@ Shortcuts to corresponding i18n [config options](#config). {.indent} ### `.messages` {.property} -The I18n bundle used for runtime messages, for example, for translated validation errors, such as `ASSERT_RANGE` or `ASSERT_FORMAT`. Translations are loaded from properties with base name `messages`, like that in the [*bookstore* sample](https://github.com/capire/bookstore/tree/main/_i18n): {.indent} +The I18n bundle used for runtime messages, for example, for translated validation errors, such as `ASSERT_RANGE` or `ASSERT_FORMAT`. Translations are loaded from properties with base name `messages`, like that in the [*bookstore* sample](https://github.com/capire/bookstore/tree/main/app/_i18n): {.indent} ```zsh cap/samples/bookshop/ @@ -114,7 +114,7 @@ cap/samples/bookshop/ ### `.labels` {.property} -The I18n bundle used for UI labels, such as `CreatedAt` or `CreatedBy`, referenced from respective [Fiori annotations](../guides/uis/i18n#externalizing-texts-bundles). Translations are loaded from properties with base name `i18n`, like that in the [*bookstore* sample](https://github.com/capire/bookstore/tree/main/_i18n): {.indent} +The I18n bundle used for UI labels, such as `CreatedAt` or `CreatedBy`, referenced from respective [Fiori annotations](../guides/uis/i18n#externalizing-texts-bundles). Translations are loaded from properties with base name `i18n`, like that in the [*bookstore* sample](https://github.com/capire/bookstore/tree/main/app/_i18n): {.indent} ```zsh cap/samples/bookshop/ diff --git a/node.js/cds-test.md b/node.js/cds-test.md index eadf66cd2f..e01f222cdb 100644 --- a/node.js/cds-test.md +++ b/node.js/cds-test.md @@ -320,7 +320,7 @@ await test.post('/browse/submitOrder', ``` > [!tip] Using Fetch API under the hood -> Under the hood, these methods use [Fetch API](https://developer.mozilla.org/docs/Web/API/FetchAPI), natively supported through the global [`fetch()`](https://nodejs.org/api/globals.html#fetch) function in Node.js since version 18. +> Under the hood, these methods use [Fetch API](https://developer.mozilla.org/docs/Web/API/Fetch_API), natively supported through the global [`fetch()`](https://nodejs.org/api/globals.html#fetch) function in Node.js since version 18. > [!info] Using Axios instead of Fetch API > Former versions of `cds.test` used [Axios](https://axios-http.com/) as the HTTP client. With the move to Fetch API, Axios is no longer included as a dependency in `@cap-js/cds-test`. However, you can still use Axios in your tests if you prefer it over Fetch API. Simply add Axios as a dependency to your project, and it will be used automatically by `cds.test` instead of Fetch API. From 8315be1e348f1deefc80f9d0f85b67c01c8904e9 Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Mon, 18 May 2026 12:57:52 +0200 Subject: [PATCH 2/6] Update reflection-api.md --- java/reflection-api.md | 1 - 1 file changed, 1 deletion(-) diff --git a/java/reflection-api.md b/java/reflection-api.md index 8efdd2dd36..1b249135d1 100644 --- a/java/reflection-api.md +++ b/java/reflection-api.md @@ -222,7 +222,6 @@ The active feature set can't be changed within an active transaction. ### Toggling SAP Fiori UI Elements - In an [SAP Fiori elements](https://www.sap.com/design-system/fiori-design-web/v1-145/discover/frameworks/sap-fiori-elements/smart-templates) application, the UI is captured with annotations in the CDS model. Hence, toggling of [SAP Fiori elements annotations](../guides/uis/fiori#fiori-annotations) is already leveraged by the above concept: To enable toggling of such annotations (and thus UI elements), it's required that the EDMX returned by the `$metadata` respects the feature vector. This is automatically achieved by maintaining different model variants according to activated features as described in the previous section. From d387fac56fa10400cd6305e906e5d3bb3061c12d Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Mon, 18 May 2026 12:58:13 +0200 Subject: [PATCH 3/6] Update reflection-api.md --- java/reflection-api.md | 1 - 1 file changed, 1 deletion(-) diff --git a/java/reflection-api.md b/java/reflection-api.md index 1b249135d1..0d5a705b53 100644 --- a/java/reflection-api.md +++ b/java/reflection-api.md @@ -224,7 +224,6 @@ The active feature set can't be changed within an active transaction. In an [SAP Fiori elements](https://www.sap.com/design-system/fiori-design-web/v1-145/discover/frameworks/sap-fiori-elements/smart-templates) application, the UI is captured with annotations in the CDS model. Hence, toggling of [SAP Fiori elements annotations](../guides/uis/fiori#fiori-annotations) is already leveraged by the above concept: To enable toggling of such annotations (and thus UI elements), it's required that the EDMX returned by the `$metadata` respects the feature vector. This is automatically achieved by maintaining different model variants according to activated features as described in the previous section. - ### Features on the Database As CDS features are reflected in database artifacts, the database needs to be upgraded when new features are _introduced_ in the CDS model. If a feature is _enabled_, the corresponding database artifacts are already present and no further database change is required. From 30b22d0fa9bdc9ecccfd5a1fff508f70a1754d14 Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Mon, 18 May 2026 13:07:53 +0200 Subject: [PATCH 4/6] move npm test --- .github/workflows/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 12915d399e..baf6679062 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -34,7 +34,6 @@ jobs: node-version: 22 cache: 'npm' - run: npm ci - - run: npm test - run: npm run lint - run: npm run docs:build env: @@ -44,6 +43,7 @@ jobs: VITE_CAPIRE_EXTRA_ASSETS: true MAVEN_HOST: https://common.repositories.cloud.sap/artifactory/build.releases MAVEN_TOKEN: ${{ secrets.MAVEN_TOKEN }} + - run: npm test - name: Upload artifact uses: actions/upload-pages-artifact@v3 with: From eae8ccb439157fcae9aeca317d8717fd2965d8de Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Mon, 18 May 2026 13:10:35 +0200 Subject: [PATCH 5/6] Update PR.yml --- .github/workflows/PR.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/PR.yml b/.github/workflows/PR.yml index 2fc4968810..9cffe251e2 100644 --- a/.github/workflows/PR.yml +++ b/.github/workflows/PR.yml @@ -33,6 +33,6 @@ jobs: npm install npm run check - run: npm ci - - run: npm test - run: npm run docs:build + - run: npm test - run: npm run lint From 981787f1eea6d4d88aee5303cd1190a8199f3366 Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Mon, 18 May 2026 13:11:28 +0200 Subject: [PATCH 6/6] more fixes --- .github/workflows/PR-SAP.yml | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/.github/workflows/PR-SAP.yml b/.github/workflows/PR-SAP.yml index cbec6b6f51..51013196ed 100644 --- a/.github/workflows/PR-SAP.yml +++ b/.github/workflows/PR-SAP.yml @@ -38,8 +38,6 @@ jobs: cache-dependency-path: docs/package-lock.json - run: npm ci working-directory: docs - - run: npm test - working-directory: docs - run: npm run lint working-directory: docs - run: npm run docs:build @@ -50,9 +48,5 @@ jobs: VITE_CAPIRE_EXTRA_ASSETS: true MAVEN_HOST: https://common.repositories.cloud.sap/artifactory/build.releases MAVEN_TOKEN: ${{ secrets.MAVEN_TOKEN }} - - name: Find broken anchor links + - run: npm test working-directory: docs - run: | - npm run docs:preview -- --port 5555 & - sleep 2 - .github/etc/blc.js http://localhost:5555/docs/