ContentVariantDisplay: add DisplayName property and use in Umbraco in… #7677
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@nielslyngsoe Seperate branch this time, probably easier to check. This is a small change which adds a
DisplayName
property to theContentVariantDisplay
class so we can control the variant display name on the server, and in AngularJS do not have to bind to functions which is slower and I know Shannon does not like that either.In addition, developers can now alter the
DisplayName
property if desired by using the existing Umbraco eventEditorModelEventManager.SendingContentModel
which is also useful for the uMarketingSuite.FYI, because this made the
contentvariantutilities.service.js
entirely obsolete (because it was empty) I removed it.This item has been added to our backlog AB#5130