Merge branch 'main' into draft-messages

Author: chgeo

.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"

.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).

java/working-with-cql/query-execution.md

@@ -282,6 +282,10 @@ UPDATE entity OrderView2
 - [Deep write](./query-execution#deep-insert-upsert) via (aliased) compositions (*lineItems*) is supported if there are corresponding compositions (*items*) in the underlying entity definition. Deep write via compositions that are only defined in the view (for example via [mixins](../../cds/cql#association-definitions)) is not supported and the data is ignored.
 - [Path expressions](../../cds/cql#path-expressions) over compositions *of one* (*header.status*) are writable. For [inserts](./query-api#insert), the view must expose all *not null* elements of the target entity and the data must include values for all of them. In the example above, the order header must have a generated key to support inserting new orders with a value for *headerStatus*.
 
+    ::: warning Handling Compositions and Aliased Paths in Projections
+    For projections that include *to-one* compositions (*header*) and aliased paths over these compositions (*headerStatus*), write structured data using the composition and make the aliased path [@readonly](../../guides/providing-services#readonly). Do not use data for the aliased path along with structured data for the composition in the same statement.
+    :::
+
     ::: warning Path Expressions over Associations
     Path expressions navigating *associations* (*header.customer.name*) are [not writable](#cascading-over-associations) by default. To avoid issues on write, annotate them with [@readonly](../../guides/providing-services#readonly).
     :::