cap-js
diff --git a/‎.github/CODEOWNERS
Lines changed: 2 additions & 1 deletion b/‎.github/CODEOWNERS
Lines changed: 2 additions & 1 deletion
diff --git a/‎.github/cds-snippet-checker/package.json
Lines changed: 1 addition & 1 deletion b/‎.github/cds-snippet-checker/package.json
Lines changed: 1 addition & 1 deletion
diff --git a/‎.vitepress/config.ts
Lines changed: 2 additions & 2 deletions b/‎.vitepress/config.ts
Lines changed: 2 additions & 2 deletions
diff --git a/‎about/features.md
Lines changed: 1 addition & 1 deletion b/‎about/features.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎about/index.md
Lines changed: 1 addition & 1 deletion b/‎about/index.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎advanced/hybrid-testing.md
Lines changed: 7 additions & 12 deletions b/‎advanced/hybrid-testing.md
Lines changed: 7 additions & 12 deletions
diff --git a/‎advanced/odata.md
Lines changed: 6 additions & 28 deletions b/‎advanced/odata.md
Lines changed: 6 additions & 28 deletions
diff --git a/‎cds/cdl.md
Lines changed: 4 additions & 1 deletion b/‎cds/cdl.md
Lines changed: 4 additions & 1 deletion
diff --git a/‎get-started/assets/jumpstart/image-20230310202845639.png
-43.5 KB b/‎get-started/assets/jumpstart/image-20230310202845639.png
-43.5 KB
diff --git a/‎get-started/assets/jumpstart/node-download-lts.png
16.9 KB b/‎get-started/assets/jumpstart/node-download-lts.png
16.9 KB
@@ -1,7 +1,8 @@
 # This files defines code ownership.
 
 # General content
-* @renejeglinsky @smahati
+* @smahati
+## * @renejeglinsky
 
 # Infra
 .github/    @chgeo @swaldmann
 
@@ -12,6 +12,6 @@
     "check": "node check-cds-snippets.js"
   },
   "dependencies": {
-    "@sap/cds-compiler": "^4.4"
+    "@sap/cds-compiler": "latest"
   }
 }
@@ -23,8 +23,8 @@ if (!siteURL.pathname.endsWith('/'))  siteURL.pathname += '/'
 const redirectLinks: Record<string, string> = {}
 
 const latestVersions = {
-  java_services: '3.0.0',
-  java_cds4j: '3.0.0'
+  java_services: '3.1.0',
+  java_cds4j: '3.1.0'
 }
 
 const localSearchOptions = {
 
@@ -143,7 +143,7 @@ Following is an index of the features currently covered by CAP, with status and
 
 > <sup>1</sup> Export CDS models to ... <br>
 > <sup>2</sup> To support customers with existing OData V2 UIs<br>
-> <sup>3</sup> Through [V2 proxy](../advanced/odata#odata-v2-proxy-node)  <br>
+> <sup>3</sup> Through [V2 proxy](../advanced/odata#odata-v2-adapter-node)  <br>
 > <sup>4</sup> Could be a good case for 3rd-party contribution <br>
 > <sup>5</sup> For Node.js try out the [GraphQL Adapter](/plugins/#graphql-adapter) <br>
 > <sup>6</sup> For Java try out the provided [sample code](https://github.com/SAP-samples/cloud-cap-samples-java/commit/16dc5d9a1f103eb1336405ee601dc7004f70538f). <br>
 
@@ -311,7 +311,7 @@ Services in CAP are **stateless** and with a **minimal footprint**, which allows
 
 <figure>
    <img src="../assets/agnostic-services.drawio.svg" width="333px">
-  <figcaption><a href="#hexagonal-architecture">Hexagonal Architecture à la CAP</a></figcaption>
+  <figcaption style="text-align: center"><a href="#hexagonal-architecture">Hexagonal Architecture à la CAP</a></figcaption>
 </figure>
 
 <br><br>
 
@@ -214,8 +214,8 @@ Alternatively, you can bind to Kubernetes **Secrets**.
 You can use the `kubectl get secrets` command to list all secrets in your current Kubernetes context:
 
 ```log
-NAME                                    TYPE                                  DATA   AGE
-bookshop-db                       Opaque                                11     44h
+NAME               TYPE      DATA   AGE
+bookshop-db        Opaque    11     44h
 ```
 
 Use the secret name for the `-2` option.
@@ -324,12 +324,10 @@ cds bind --exec mvn spring-boot:run
 Instead of binding to specific cloud services, you can bind to all supported service bindings of an application running on the SAP BTP Cloud Foundry environment:
 
 ```sh
+cds bind -a bookshop-srv # ...or the spelled out way:
 cds bind --to-app-services bookshop-srv
 ```
-
-::: tip
-This shortcut is only possible if you don't need to provide a `service` or a `kind`.
-:::
+> This shortcut is only possible if you don't need to provide a `kind`.
 
 ## `cds bind` Usage { #cds-bind-usage}
 
@@ -378,10 +376,7 @@ There is a handy shortcut to bind multiple services with one command:
 ```sh
 cds bind -2 bookshop-db,bookshop-auth
 ```
-
-::: tip
-This shortcut is only possible if you don't need to provide a `service` or a `kind`.
-:::
+> This shortcut is only possible if you don't need to specify a `kind`.
 
 ### Overwrite Cloud Service Credentials { #overwriting-service-credentials}
 
@@ -498,7 +493,7 @@ Learn how to do hybrid testing using the XSUAA service in the [CAP Node.js authe
 Configure your required bindings for testing and save them to your project's _package.json_ file for your tests' profile:
 
 ```sh
-cds bind -2 integration-test-hana -o package.json -p integration-test
+cds bind -2 integration-test-hana -o package.json -4 integration-test
 ```
 
 No credentials are saved!
@@ -531,6 +526,6 @@ With `CDS_ENV`, you specify the configuration profile for the test, where you pr
 
 `cds env get requires` prints the `requires` section of the configuration as a JSON string. By adding the `--resolve-bindings` option, it includes the credentials of the service bindings from the cloud. To make the credentials available for all subsequent `cds` commands and the tests, the `requires` JSON string is put into the `cds_requires` variable.
 
-::: tip
+::: tip Allow dynamic deploy targets
 Service bindings created by `cds bind` contain the Cloud Foundry API endpoint, org, and space. You can allow your services to connect to the currently targeted Cloud Foundry org and space by removing these properties from the binding structure.
 :::
@@ -1324,42 +1324,20 @@ Since singletons  represent a one-element entity, a `POST` request is not suppor
 
 While CAP defaults to OData V4, the latest protocol version, some projects need to fallback to OData V2, for example, to keep using existing V2-based UIs.
 
-### Enabling OData V2 via Proxy in Node.js Apps { #odata-v2-proxy-node}
+### Enabling OData V2 via CDS OData V2 Adapter in Node.js Apps { #odata-v2-adapter-node}
 
 CAP Node.js supports serving the OData V2 protocol through the [_OData V2 adapter for CDS_](https://www.npmjs.com/package/@cap-js-community/odata-v2-adapter), which translates between the OData V2 and V4 protocols.
 
-For Node.js projects, add the proxy as express.js middleware as follows:
+For Node.js projects, add the CDS OData V2 adapter as express.js middleware as follows:
 
 1. Add the adapter package to your project:
 
     ```sh
     npm add @cap-js-community/odata-v2-adapter
     ```
 
-2. Add this as a plugin to your project:
-
-    ::: code-group
-    ```json [package.json]
-    {...
-    "cds" : {
-      "cov2ap" : {
-        "plugin" : true
-        }
-      }
-    }
-    ```
-
-    ```json [.cdsrc.json]
-    {
-    "cov2ap" : {
-      "plugin" : true
-      }
-    }
-    ```
-    :::
-
-3. Access OData V2 services at [http://localhost:4004/v2/${path}](http://localhost:4004/v2).
-4. Access OData V4 services at [http://localhost:4004/${path}](http://localhost:4004) (as before).
+2. Access OData V2 services at [http://localhost:4004/odata/v2/${path}](http://localhost:4004/odata/v2).
+3. Access OData V4 services at [http://localhost:4004/odata/v4/${path}](http://localhost:4004/odata/v4) (as before).
 
 Example: Read service metadata for `CatalogService`:
 
@@ -1370,8 +1348,8 @@ Example: Read service metadata for `CatalogService`:
     service CatalogService { ... }
     ```
 
-- OData V2: `GET http://localhost:4004/v2/browse/$metadata`
-- OData V4: `GET http://localhost:4004/browse/$metadata`
+- OData V2: `GET http://localhost:4004/odata/v2/browse/$metadata`
+- OData V4: `GET http://localhost:4004/odata/v4/browse/$metadata`
 
 [Find detailed instructions at **@cap-js-community/odata-v2-adapter**.](https://www.npmjs.com/package/@cap-js-community/odata-v2-adapter){.learn-more}
 
 
@@ -1105,7 +1105,10 @@ Each path in the expression is checked:
 * If the annotation is assigned to a subelement of a structured element, the top level
   elements of the entity can be accessed via `$self`.
 * A parameter `par` can be accessed via `:par`, just like parameters of a parametrized entity in queries.
-* If a path cannot be resolved successfully, compilation fails with an error.
+* The draft specific element `IsActiveEntity` can be referred to with the magic variable `$draft.IsActiveEntity`.
+  During draft augmentation `$draft.IsActiveEntity` is rewritten to `$self.IsActiveEntity` for all draft enabled
+  entities (root and sub nodes but not for named types or entity parameters).
+* If a path can't be resolved successfully, compilation fails with an error.
 
 In contrast to `@aReference: foo.bar`, a single reference written as expression `@aRefExpr: ( foo.bar )`
 is checked by the compiler.
Original file line number	Diff line number	Diff line change
`@@ -12,6 +12,6 @@`
`12`	`12`	`"check": "node check-cds-snippets.js"`
`13`	`13`	`},`
`14`	`14`	`"dependencies": {`
`15`		`- "@sap/cds-compiler": "^4.4"`
	`15`	`+ "@sap/cds-compiler": "latest"`
`16`	`16`	`}`
`17`	`17`	`}`
Original file line number	Diff line number	Diff line change
`@@ -23,8 +23,8 @@ if (!siteURL.pathname.endsWith('/')) siteURL.pathname += '/'`
`23`	`23`	`const redirectLinks: Record<string, string> = {}`
`24`	`24`
`25`	`25`	`const latestVersions = {`
`26`		`- java_services: '3.0.0',`
`27`		`- java_cds4j: '3.0.0'`
	`26`	`+ java_services: '3.1.0',`
	`27`	`+ java_cds4j: '3.1.0'`
`28`	`28`	`}`
`29`	`29`
`30`	`30`	`const localSearchOptions = {`