Table of Contents

Breaking Changes in EAV and 2sxc 16

Breaking Changes in EAV and 2sxc v16

We try to minimize breaking changes, and most breaking changes won't affect your work, because it's internal API. We're documenting it here to ensure you know what happened, in case you still run into this.

Summary

V16.00 doesn't have breaking changes; 16.02 has some very minor breaking changes

Breaking Changes in 2sxc 16.02

API Changes which affect you if you had installed v16.01 with the latest Blog or Mobius

In v16.01 we had introduced a new Typed API, which turned out to be not good-enough.

This meant we had to rollback some of the changes we had introduced there,

API Changes which should really not affect you

  1. Various APIs which used to return an IHybridHtmlString now return an IRawHtml
    This is to sync types with RazorBlade. It should have no effect on any code out there, as the result type is usually dynamic
  2. Renamed the type ToSic.Sxc.Data.IDynamicMetadata to ToSic.Sxc.Data.IMetadata
    This is technically a breaking change, but the type name should never have been used in any razor code, so it shouldn't affect anybody.
  3. Renamed ToSic.Sxc.Data.IDynamicField to ToSic.Sxc.Data.IField
    This is technically a breaking change, but the type name should never have been used in any razor code, so it shouldn't affect anybody.

Breaking Changes in 2sxc 16.03

API Changes which affect you if you had installed v16.01/16.02 with the latest Blog or Mobius

  1. Base classes were renamed because of confusing ...Pro suffix. RazorPro is now RazorTyped, ApiPro is ApiTyped and CodePro is CodeTyped #3147
  2. Now by default, all access to a property like .String("SomeName") will throw an error in required mode if the field doesn't exist #3138
  3. The .Parents(...) was enhanced to require named parameters (see blog post) #3139
Edit this page