From 5d643741be788d25d891c4dc6a1157c76608bd68 Mon Sep 17 00:00:00 2001 From: Dawid Rutkowski <33089653+sc-dawidrutkowski@users.noreply.github.com> Date: Fri, 25 Oct 2019 15:10:54 +0200 Subject: [PATCH] #348713Explicitly state that field names are not affected by the serialization configuration on Layout Service (#284) * #348713 Explicitly state that field names are not affected by the serialization configuration on Layout Service * #348713 Update --- .../extending-layout-service-overview/en.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/data/routes/docs/techniques/extending-layout-service/extending-layout-service-overview/en.md b/docs/data/routes/docs/techniques/extending-layout-service/extending-layout-service-overview/en.md index 79e54ec5a0..64f8e52818 100644 --- a/docs/data/routes/docs/techniques/extending-layout-service/extending-layout-service-overview/en.md +++ b/docs/data/routes/docs/techniques/extending-layout-service/extending-layout-service-overview/en.md @@ -117,6 +117,7 @@ The Layout Service JSON rendering process is highly configurable, and allows you ``` +> In terms of modifying serialization configuration, keep in mind that you can change the whole JSON beside field names. Field names can be changed in Sitecore, if you need to e.g.: have them camel-cased, you need do it in Sitecore. So basically serialization configuration is responsible for changing JSON on which user don't have influence. ### Using a custom Layout Service configuration with JSS