BranchID deserialization possible again

Rainbow was fitted with updated deserialization code so special handling around BranchID is no longer required. More info here: https://github.com/SitecoreUnicorn/Unicorn/releases/tag/4.1.5

BranchID is now back. Fully.

So the BranchID bug that has been around in (at least) all of the 9.x releases was fixed in 10.1. Turns out the implementation fix, if applied to Rainbows deserializer, also works retroactively.

So in short, BranchID handling is now fully back and will be in effect everywhere.

BranchID handling updated, again

Revisited the whole BranchID handling.

For those not in the loop, basically deserializing an item that was originally created from a Branch Template into a Sitecore instance where this item does not exist yet will cause Shared field values to go missing. Don't ask me why, you really do not want to get me started.

To be clear, this is not a Rainbow problem. It happens with the built-in serializer as well as the Sitecore Packager. This is why you often need to install SXA packages twice or more times to get all the field values in place.

Anyway.

After testing this behaviour on Sitecore 10.1 I can confirm that the problem has been resolved.

So from henceforth; Rainbow will now completely ignore BranchID for items when running on Sitecore versions < 10.1. As has previously been discussed there should be no practical impact from this.

On Sitecore versions 10.1 and forward, BranchID is now included and considered.

BranchId handling disabled

BranchId is now completely ignored by the serialization and deserialization code. Longer explanation to follow.

Minor fix for cache/dirty item tracking

• Updated items would not always get published due to some overzealous dirty item cache handling. See #38

Thanks to Zaheer Tariq (https://github.com/zaheer-tariq) for the PR to address this issue.

2.1.1 Release

Includes changes that allows for better "dirty tracking" of items under influence of Field Transforms.

Rise of the Unicorn Transformers

2.1.0 Release

Described in more detail here: https://intothecloud.blog/2019/05/26/Rise-of-the-Unicorn-Transformers/

Also includes necessary fixes for Sitecore 9.2 compatibility. For Sitecore 9.2 and up, upgrade to this version is necessary

Field Handling stability and consistency

Field Handling stability and consistency

Mostly a bugfixing release. Some of these bugs could have a potentially large impact, so upgrading to this version is recommended.

Change notes

• Small change to what triggers a Sitecore field value to be reset (to std value). Rainbow would skip this, for fields that already were .NullOrEmpty - but an unchecked checkbox field is empty and a reset one is null. Now it resets correctly for any value not null.

• Added constructor overload to the DefaultDeserializer, to remain compatible with SideKick and other potential projects that have not yet been updated.

• The ItemComparer will no longer attempt to find a Field Comparer for null/null values, it will now assume them to be identical. This should help untangle SitecoreUnicorn/Unicorn#319.

• Fixes SitecoreUnicorn/Unicorn#334 - Changes in Sitecore's internal handling of shared/versioned/unversioned field values conflicted with Rainbow's handling of same

• Another fix for Unicorn Issue #319 - Empty field values would not get written back to Sitecore if no field value existed (e.g. field contained standard value)

• Fixes SitecoreUnicorn/Unicorn#324 - Leading and trailing spaces in predicate names are now trimmed.

• Fixes #30 - Do not reset fields which are excluded in the fieldFilter (#31). Ignored fields would get reset to standard value if other fields on the item updated.

Thanks to @JeffDarchuk and @NaibafCH for their valuable contributions to this release.

Ignored fields no longer gets reset

As described in #30

Filtered fields would get reset during Sync if the item in question had changed field values (for non-ignored fields).

Thanks to @NaibafCH for noticing this and even submitting a fix. With corresponding unit tests and all :-)

Minor fix regarding leading and trailing spaces

Configuration names are now trimmed for leading and trailing spaces. See SitecoreUnicorn/Unicorn#324