From 33b317cd6335c59d5ece659b83354b25cfdbece7 Mon Sep 17 00:00:00 2001 From: Vladislav Leonkev Date: Mon, 17 Aug 2026 12:32:26 +0200 Subject: [PATCH 1/4] docs: clarify and refine PUT vs PATCH explanation Rewrite the description of the PUT HTTP method for clarity and correctness. - Fix grammar error ("doesn't yet exists" -> corrected phrasing) - Condense fragmented sentences into a single, readable statement - Introduce parallel structure ("a missing resource" / "an existing one") to clearly contrast the two PUT scenarios - Preserve original meaning while improving flow and readability --- node.js/cds-serve.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/node.js/cds-serve.md b/node.js/cds-serve.md index 3632940fb1..ec70baae60 100644 --- a/node.js/cds-serve.md +++ b/node.js/cds-serve.md @@ -406,10 +406,9 @@ Be aware that using an absolute path will disallow serving the service at multip ### PATCH vs. PUT vs. Replace -The HTTP method `PATCH` is meant for partial modification of an _existing resource_. -`PUT`, on the other hand, is meant for ensuring a resource exists -, that is, if it doesn't yet exists, it gets created. -If it does exist, it gets updated to reflect the request's content. +The HTTP method `PATCH` is meant for partial modification of an _existing resource_. +`PUT`, on the other hand, ensures a resource exists: a missing resource gets created, +while an existing one gets updated with the request’s content. This content, however, may be incomplete. By default, the values for not listed keys are not touched. From 646c70fde76b0c6caf0050d6c4392656f1fc3e1d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Jeglinsky?= Date: Mon, 17 Aug 2026 20:22:27 +0200 Subject: [PATCH 2/4] Apply suggestion from @renejeglinsky --- node.js/cds-serve.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node.js/cds-serve.md b/node.js/cds-serve.md index ec70baae60..69c95be818 100644 --- a/node.js/cds-serve.md +++ b/node.js/cds-serve.md @@ -408,7 +408,7 @@ Be aware that using an absolute path will disallow serving the service at multip The HTTP method `PATCH` is meant for partial modification of an _existing resource_. `PUT`, on the other hand, ensures a resource exists: a missing resource gets created, -while an existing one gets updated with the request’s content. +while an existing one gets updated with the request's content. This content, however, may be incomplete. By default, the values for not listed keys are not touched. From 5f4c6c09cd055d2985bb05250cbe94c60d4e83e7 Mon Sep 17 00:00:00 2001 From: Vladislav Leonkev <131776471+vl-leon@users.noreply.github.com> Date: Tue, 18 Aug 2026 14:59:09 +0200 Subject: [PATCH 3/4] Apply suggestion from @vl-leon --- node.js/cds-serve.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node.js/cds-serve.md b/node.js/cds-serve.md index 69c95be818..c903c1b83e 100644 --- a/node.js/cds-serve.md +++ b/node.js/cds-serve.md @@ -411,7 +411,7 @@ The HTTP method `PATCH` is meant for partial modification of an _existing reso while an existing one gets updated with the request's content. This content, however, may be incomplete. -By default, the values for not listed keys are not touched. +By default, the values for not listed fields are not touched. The rationale being that default values are known and clients have the option to send full representations, if necessary. The following table shows the Node.js runtime's configuration options and their respective default value: From c4cb4f1fe8913a733435765822ccb15e80abfabd Mon Sep 17 00:00:00 2001 From: Vladislav Leonkev <131776471+vl-leon@users.noreply.github.com> Date: Tue, 18 Aug 2026 15:00:59 +0200 Subject: [PATCH 4/4] Apply suggestion from @vl-leon --- node.js/cds-serve.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node.js/cds-serve.md b/node.js/cds-serve.md index c903c1b83e..1076d41eb5 100644 --- a/node.js/cds-serve.md +++ b/node.js/cds-serve.md @@ -412,7 +412,7 @@ while an existing one gets updated with the request's content. This content, however, may be incomplete. By default, the values for not listed fields are not touched. -The rationale being that default values are known and clients have the option to send full representations, if necessary. +The rationale is that default values are known and clients have the option to send full representations, if necessary. The following table shows the Node.js runtime's configuration options and their respective default value: