From 4bf0683a1a4f79d0378ffbed8446e5cde86ae31a Mon Sep 17 00:00:00 2001 From: Johannes Vogel <31311694+johannes-vogel@users.noreply.github.com> Date: Thu, 22 Feb 2024 16:46:51 +0100 Subject: [PATCH] fix: ad-hoc options are not cached (#698) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * fix: ad-hoc options are not cached * Update node.js/cds-connect.md --------- Co-authored-by: René Jeglinsky --- node.js/cds-connect.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/node.js/cds-connect.md b/node.js/cds-connect.md index d0b38f721..f253666c4 100644 --- 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.