Planned Breaking Changes in CMS UI 2016
Remove support for legacy dot notation for dojo modules
We are removing the support for the legacy dot notation for dojo modules, e.g. epi-cms.editing.ContentPicker. This means that you need to change all EditorDescriptors, Components etc where you have defined your Dojo modules using the . to /.
It is really important that you change the code to use the AMD path syntax (/) in your code, both in C# and Javascript.
We have had support for AMD Path notation for a long time, so you can start changing your code to the slash AMD path notation right away. There is no need to wait for CMS 10.
From (Dot notation):
epi-cms.editing.ContentPicker
To (AMD path):
epi-cms/editing/ContentPicker
Aliases for epi/cms widgets are removed
As a result of the above mentioned changes to remove support for dot notation we’ve also removed the aliases that made it possible to require epi-cms widgets using epi/cms. Change your dependecies to use epi-cms.
epi/cms/form/SearchTextBox
From:
epi/cms/form/SearchTextBox
To:
epi-cms/form/SearchTextBox
epi/cms/form/PageInfoPicker
From:
epi/cms/form/PageInfoPicker
To:
epi-cms/form/PageInfoPicker
Objects of type epi._Dependency can no longer be created
Instead require the singleton dependency object “epi/dependency”.
EPiServer.Cms.Shell.UI.Rest.ContentQuery.GetContentByPermanentLinkQuery
GetContentByPermanentLinkQuery will always return the content without work id. It will ignore the “stripWorkId” parameter, it has also been moved into the EPiServer.Cms.Shell.UI.Rest.ContentQuery.Internal namespace
Dialog now has destroyOnHide:true by default
Set destroyOnHide to false if to keep the dialog around after it’s hidden. Otherwise there’s no need to set the value as we want to destroy dialogs by default to avoid memory leaks.
EPiServer.Cms.Shell.UI.Rest.Models.ExtendedVersionStatus
The value of ExtendedVersionStatus.Expired has been changed. Also added the new status ExtendedVersionStatus.AwaitingApproval, it has also been moved into the EPiServer.Cms.Shell.UI.Rest.Models.Internal
Calling watchModelChange and unwatchModelChange on _Command.js has been deprecated
Commands should always be allowed to update their internal state based on the current model.
Internal API
We are moving a lot of code that we consider to be part of our internal implementations into an Internal namespace. The full list will be available when we are closing in on the release.
Comments