fix: ad-hoc options are not cached (#698)

* fix: ad-hoc options are not cached * Update node.js/cds-connect.md --------- Co-authored-by: René Jeglinsky <[email protected]>
cap-js · Feb 22, 2024 · 4bf0683 · 4bf0683
1 parent 2a5c0c4
commit 4bf0683
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/node.js/cds-connect.md b/node.js/cds-connect.md
@@ -191,7 +191,9 @@ _**Arguments:**_
 
 _**Caching:**_
 
-Service instances are cached in [`cds.services`](cds-facade#cds-services), thus subsequent connects with the same service name return the initially connected one. As services constructed by [`cds.serve`] are registered with [`cds.services`](cds-facade#cds-services) as well, a connect finds and returns them as local service connections.
+Service instances are cached in [`cds.services`](cds-facade#cds-services), thus subsequent connects with the same service name return the initially connected one. As services constructed by [`cds.serve`](cds-serve#cds-serve) are registered with [`cds.services`](cds-facade#cds-services) as well, a connect finds and returns them as local service connections.
+
+If _ad-hoc_ options are provided, the instance is not cached.