Usync Exporter - UI showing unexpected hidden char differences in Checkbox list item
Hi Kevin
Umb 13.3.2 and Usync Complete 13.1.4
Got a query regarding usync exporter.
Building a package which includes nodes with nested content properties with a checkbox list on them.
Package is uploading and seems to be applied fine. However, when playing that same package back it is showing these differences which were not there before.
Applying the package again does not change anything.
It looks like this is the difference in how the JSON is being serialized inside the block - it shouldn't cause any issues (hopefully),
its the way the content is either serialized with indentation on or off. by default on most properties we serialize with it on (i think) but for block/nested elements its a little diffrent, because it can get complicated when they are blocks within blocks etc. (and it can be slightly diffrent in umbraco when an item is saved via the back office vs when its opens and saved in code (to do with how the angualr in the back office serizlises it).
but in terms of performance site rendering if you are using the Json methods to parse the string the change in format shouldn't matter.
if you wanted to get rid of it completely then if you had a custom value mapper for the property, that would determine the format of the string that is serialized and deserilized from the content.
there are a few places where you can see how mappers are made :
Usync Exporter - UI showing unexpected hidden char differences in Checkbox list item
Hi Kevin
Umb 13.3.2 and Usync Complete 13.1.4
Got a query regarding usync exporter.
Building a package which includes nodes with nested content properties with a checkbox list on them.
Package is uploading and seems to be applied fine. However, when playing that same package back it is showing these differences which were not there before.
Applying the package again does not change anything.
Everything works, seems like a UI bug.
Cheers
Jules
Hi Jules,
It looks like this is the difference in how the JSON is being serialized inside the block - it shouldn't cause any issues (hopefully),
its the way the content is either serialized with indentation on or off. by default on most properties we serialize with it on (i think) but for block/nested elements its a little diffrent, because it can get complicated when they are blocks within blocks etc. (and it can be slightly diffrent in umbraco when an item is saved via the back office vs when its opens and saved in code (to do with how the angualr in the back office serizlises it).
but in terms of performance site rendering if you are using the Json methods to parse the string the change in format shouldn't matter.
if you wanted to get rid of it completely then if you had a custom value mapper for the property, that would determine the format of the string that is serialized and deserilized from the content.
there are a few places where you can see how mappers are made :
is working on a reply...