Fix name

Author: daogrady

tools/cds-lint/examples/no-cross-service-import/correct/srv/admin-service.js

@@ -0,0 +1,6 @@
+const cds = require('@sap/cds')
+const { Books } = require('#cds-models/sap/capire/bookshop/AdminService') // [!code error]
+
+module.exports = class AdminService extends cds.ApplicationService {
+  // …
+}

tools/cds-lint/examples/no-cross-service-import/incorrect/srv/admin-service.js

@@ -0,0 +1,6 @@
+const cds = require('@sap/cds')
+const { Books } = require('#cds-models/sap/capire/bookshop/CatalogService') // [!code highlight]
+
+module.exports = class AdminService extends cds.ApplicationService {
+  // …
+}

…r-variables/correct/srv/admin-service.js …er-variable/correct/srv/admin-service.jstools/cds-lint/examples/no-shared-handler-variables/correct/srv/admin-service.js renamed to tools/cds-lint/examples/no-shared-handler-variable/correct/srv/admin-service.js tools/cds-lint/examples/no-shared-handler-variables/correct/srv/admin-service.js renamed to tools/cds-lint/examples/no-shared-handler-variable/correct/srv/admin-service.js

@@ -0,0 +1,43 @@
+---
+status: released
+---
+
+<script setup>
+  import PlaygroundBadge from '../components/PlaygroundBadge.vue'
+</script>
+
+# no-cross-service-import
+
+## Rule Details
+
+This rule helps you avoid importing artifacts generated for one service (e.g., service X) into the implementation of another service (e.g., service Y) when using cds-typer. Keeping service boundaries clear makes your codebase easier to maintain and understand.
+
+#### Version
+This rule was introduced in `@sap/eslint-plugin-cds 4.0.2`.
+
+## Examples
+
+### ✅ &nbsp; Correct example
+
+Here, the imported entity belongs to `AdminService` and is used within the implementation of `AdminService` itself—this is the recommended approach:
+::: code-group
+<<< ../examples/no-cross-service-import/correct/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+:::
+<PlaygroundBadge
+  name="no-cross-service-import"
+  kind="correct"
+  :files="['srv/admin-service.js']"
+/>
+
+### ❌ &nbsp; Incorrect example
+
+In this case, an entity from `CatalogService` is imported into the implementation of `AdminService`. This cross-service import is discouraged, as it can lead to confusion and maintenance issues:
+
+::: code-group
+<<< ../examples/no-cross-service-import/incorrect/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+:::
+<PlaygroundBadge
+  name="no-cross-service-import"
+  kind="incorrect"
+  :files="['srv/admin-service.js']"
+/>

…variables/incorrect/srv/admin-service.js …-variable/incorrect/srv/admin-service.jstools/cds-lint/examples/no-shared-handler-variables/incorrect/srv/admin-service.js renamed to tools/cds-lint/examples/no-shared-handler-variable/incorrect/srv/admin-service.js tools/cds-lint/examples/no-shared-handler-variables/incorrect/srv/admin-service.js renamed to tools/cds-lint/examples/no-shared-handler-variable/incorrect/srv/admin-service.js

@@ -6,7 +6,7 @@ status: released
   import PlaygroundBadge from '../components/PlaygroundBadge.vue'
 </script>
 
-# no-shared-handler-variables
+# no-shared-handler-variable
 
 ## Rule Details
 
@@ -25,10 +25,10 @@ This rule was introduced in `@sap/eslint-plugin-cds 4.0.2`.
 In the following example, only locally defined variables are used within handler implementation:
 
 ::: code-group
-<<< ../examples/no-shared-handler-variables/correct/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+<<< ../examples/no-shared-handler-variable/correct/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
 :::
 <PlaygroundBadge
-  name="no-shared-handler-variables"
+  name="no-shared-handler-variable"
   kind="correct"
   :files="['srv/admin-service.js']"
 />
@@ -38,10 +38,10 @@ In the following example, only locally defined variables are used within handler
 In the following example, the variables `newBook` and `readBooks` are declared in scopes surrounding the handler function, making their value available to subsequent calls of that handler. While this may seem advantageous, it can cause issues in a multitenant scenario, where the handler function can be invoked by multiple tenants.
 
 ::: code-group
-<<< ../examples/no-shared-handler-variables/incorrect/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
+<<< ../examples/no-shared-handler-variable/incorrect/srv/admin-service.js#snippet{js:line-numbers} [srv/admin-service.js]
 :::
 <PlaygroundBadge
-  name="no-shared-handler-variables"
+  name="no-shared-handler-variable"
   kind="incorrect"
   :files="['srv/admin-service.js']"
 />