Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#348713Explicitly state that field names are not affected by the serialization configuration on Layout Service #284

Merged
merged 2 commits into from
Oct 25, 2019
Merged

#348713Explicitly state that field names are not affected by the serialization configuration on Layout Service #284

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2a38f2b
#348713 Explicitly state that field names are not affected by the ser…
sc-dawidrutkowski Oct 25, 2019
c3435f2
#348713 Update
sc-dawidrutkowski Oct 25, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...ocs/techniques/extending-layout-service/extending-layout-service-overview/en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,7 @@ The Layout Service JSON rendering process is highly configurable, and allows you
</serialization>
</config>
```
> 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

Expand Down