You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Without uSync.Complete, the configuration for a block list is immediately serialized using JsonConvert.SerializeObject, with json settings using uSyncContractResolver to handle ordering the properties alphabetically. See line here
uSync.Complete appears to add a data type serializer for block lists that does not use these same json settings to order the properties, resulting in different file structures depending on if you have this installed or not.
This causes an issue for us as we programmatically generate these files for multiple projects, some using uSync.Complete and others not, causing half our projects to show changes due to the slightly difference in the structure of these files.
Version (please complete the following information):
Umbraco Version: 13.5.2
uSync Version: 13.2.5
uSync.Complete Version: 13.1.8
To Reproduce
Steps to reproduce the behavior:
With only the uSync nuget package installed, create and/or save a block list data type.
Observe the order of the Config property in the generated config file is alphabetical:
Describe the bug
Without uSync.Complete, the configuration for a block list is immediately serialized using
JsonConvert.SerializeObject
, with json settings usinguSyncContractResolver
to handle ordering the properties alphabetically. See line hereuSync.Complete appears to add a data type serializer for block lists that does not use these same json settings to order the properties, resulting in different file structures depending on if you have this installed or not.
This causes an issue for us as we programmatically generate these files for multiple projects, some using uSync.Complete and others not, causing half our projects to show changes due to the slightly difference in the structure of these files.
Version (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Config
property in the generated config file is alphabetical:Expected behavior
The JSON should always be ordered alphabetically, per the 10.1 file format
The text was updated successfully, but these errors were encountered: