Merge branch 'main' into typed-result

Author: MattSchur

.github/cds-snippet-checker/package.json

@@ -6,7 +6,7 @@
   "main": "check-cds-snippets.js",
   "author": "SAP SE (https://www.sap.com)",
   "license": "SEE LICENSE IN LICENSE",
-  "repository": "cap-js/docs",
+  "repository": "capire/docs",
   "homepage": "https://cap.cloud.sap/",
   "scripts": {
     "check": "node check-cds-snippets.js"

.github/java-snippet-checker/package.json

@@ -6,7 +6,7 @@
   "main": "check-java-snippets.js",
   "author": "SAP SE (https://www.sap.com)",
   "license": "SEE LICENSE IN LICENSE",
-  "repository": "cap-js/docs",
+  "repository": "capire/docs",
   "homepage": "https://cap.cloud.sap/",
   "scripts": {
     "check": "node check-java-snippets.js"

.github/workflows/PR-SAP.yml

@@ -9,6 +9,9 @@ concurrency:
   group: pr-sap-${{ github.workflow }}-${{ github.head_ref || github.run_id }}
   cancel-in-progress: true
 
+permissions:
+  contents: read
+
 jobs:
   build-sap:
     runs-on: ubuntu-latest

.github/workflows/PR.yml

@@ -8,6 +8,9 @@ concurrency:
   group: pr-${{ github.workflow }}-${{ github.head_ref || github.run_id }}
   cancel-in-progress: true
 
+permissions:
+  contents: read
+
 jobs:
   build:
     runs-on: ubuntu-latest

.vitepress/config.js

@@ -43,10 +43,10 @@ const config = defineConfig({
     logo: '/cap-logo.svg',
     outline: [2,3],
     socialLinks: [
-      { icon: 'github', link: 'https://github.com/cap-js/docs' }
+      { icon: 'github', link: 'https://github.com/capire/docs' }
     ],
     editLink: {
-      pattern: 'https://github.com/cap-js/docs/edit/main/:path'
+      pattern: 'https://github.com/capire/docs/edit/main/:path'
     },
     footer: {
       message: `

.vitepress/theme/components/WasThisHelpful.vue

@@ -44,7 +44,7 @@
 
     <p class="more-feedback" v-if="feedbackSelected">
       More to say?
-      <a href="https://github.com/cap-js/docs/issues" target="_blank">
+      <a href="https://github.com/capire/docs/issues" target="_blank">
         Report an issue.
       </a>
     </p>

.vitepress/theme/styles.scss

@@ -112,6 +112,20 @@ main {
       padding-left: 2.5em;
     }
 
+    // Custom list styles for nested items
+    ul {
+      list-style-type: disc; // First level: filled circle
+      
+      ul {
+        list-style-type: circle; // Second level: empty circle
+        
+        
+        ul {
+          list-style-type: square; // Third level: square
+        }
+      }
+    }
+
     .step-by-step {
       ol {
         counter-reset: my-counter;

README.md

@@ -1,6 +1,6 @@
 # Documentation for <br> SAP Cloud Application Programming Model
 
-[![REUSE status](https://api.reuse.software/badge/github.com/cap-js/docs)](https://api.reuse.software/info/github.com/cap-js/docs)
+[![REUSE status](https://api.reuse.software/badge/github.com/capire/docs)](https://api.reuse.software/info/github.com/capire/docs)
 
 ## About this project
 
@@ -10,7 +10,7 @@ Along with additional SAP-specific pages the content is published to https://cap
 
 ## Support, Feedback, Contributing
 
-This project is open to feature requests/suggestions, bug reports, etc. via [GitHub issues](https://github.com/cap-js/docs/issues) and [pull requests](https://github.com/cap-js/docs/pulls). Contribution and feedback are encouraged and always welcome.
+This project is open to feature requests/suggestions, bug reports, etc. via [GitHub issues](https://github.com/capire/docs/issues) and [pull requests](https://github.com/capire/docs/pulls). Contribution and feedback are encouraged and always welcome.
 
 See our [contribution guidelines](CONTRIBUTING.md) for information about how to contribute, the project structure, as well as additional contribution information.
 
@@ -19,7 +19,7 @@ See our [contribution guidelines](CONTRIBUTING.md) for information about how to
 If you contribute often to the documentation it's best to create your own fork, clone it to your local machine.
 
 ```sh
-git clone https://github.com/cap-js/docs   # or whatever your fork's URL is
+git clone https://github.com/capire/docs   # or whatever your fork's URL is
 ```
 
 Install the dependencies:
@@ -53,4 +53,4 @@ We as members, contributors, and leaders pledge to make participation in our com
 
 ## Licensing
 
-Copyright 2023-2025 SAP SE or an SAP affiliate company and CAP contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/cap-js/docs).
+Copyright 2023-2025 SAP SE or an SAP affiliate company and CAP contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/capire/docs).

about/features.md

@@ -47,10 +47,13 @@ Following is an index of the features currently covered by CAP, with status and
 | [Compile cds models to different outputs](../node.js/cds-compile)          | `cds compile <models>`     |
 | [Run your services in local server](../node.js/cds-serve)                  | `cds serve <services>`     |
 | [Run and restart on file changes](../get-started/in-a-nutshell)            | `cds watch`                |
-| [Read-eval-event loop](../node.js/cds-env#cli)  <!-- TODO -->              | `cds repl`                 |
+| [Read-eval-event loop](../node.js/cds-env#cli)                             | `cds repl`                 |
 | Inspect effective configuration                                            | `cds env`                  |
 | Prepare for deployment                                                     | `cds build`                |
-| Deploy to databases or cloud                                               | `cds deploy`               |
+| Deploy to databases                                                        | `cds deploy`               |
+| Build and deploy your application to the cloud                             | `cds up`                   |
+| Bind application to remote services                                        | `cds bind`                 |
+| Debug your application                                                     | `cds debug`                |
 | Login to multitenant SaaS application                                      | `cds login <app-url>`      |
 | Upgrade SaaS tenant(s) to latest versions                                  | `cds upgrade`              |
 | Logout from multitenant SaaS application                                   | `cds logout`               |

advanced/fiori.md

@@ -466,12 +466,38 @@ POST /odata/v4/AdminService/Books(ID=a11fb6f1-36ab-46ec-b00c-d379031e817a,IsActi
 Content-Type: application/json
 
 {}
-
+```
 
 For more details, see the [official UI5 documentation](https://ui5.sap.com/#/topic/ed9aa41c563a44b18701529c8327db4d).
 
 ### Validating Drafts
 
+With Fiori draft state messages, you benefit from the following improvements without any change in your application code:
+- The UI displays error messages for annotation-based validations (such as `@mandatory` or `@assert...`) while editing drafts.
+- You can register [custom validations](#custom-validations) to the `PATCH` event and write (error) messages. The draft choreography ensures the invalid value still persists.
+- Messages remain visible in the UI, even after editing other fields.
+- The UI automatically loads messages when reopening a previously edited draft.
+CAP generates side-effect annotations in the EDMX to instruct UI5 to fetch state messages after every `PATCH` request. To control side-effect annotations more precisely, override or disable them per entity:
+
+  ```cds
+  // Setting `null` disables the side-effect annotation for always fetching messages.
+  annotate MyService.MyEntity with @Common.SideEffects #alwaysFetchMessages: null;
+  ```
+
+For this feature to work correctly, CAP adds additional elements to your draft-enabled entities and [`DraftAdministrativeData`](/guides/security/data-protection-privacy#dpp-cap) to store and serve the state messages. CAP runtimes persist (error) messages for draft-enabled entities.
+
+::: warning Requires Schema Update
+This feature initiates a database schema update, as it adds an additional element to `DraftAdministrativeData`.
+:::
+
+::: warning Requires OData V4 and UI5 version >=1.135.0
+State messages require UI5 to use _document URLs_. CAP sets the `@Common.AddressViaNavigationPath` annotation to enable this. You need OData V4 and UI5 version >= 1.135.0. OData V2 does not support this annotation.
+:::
+To disable this feature, set <Config>cds.fiori.draft_messages:false</Config>.
+
+
+#### Custom Validations
+
 You can add [custom handlers](../guides/providing-services#custom-logic) to add specific validations, as usual. In addition, for a draft, you can register handlers to the respective `UPDATE` events to validate input per field, during the edit session, as follows.