Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ContentVariantDisplay: add DisplayName property and use in Umbraco in… #7677

Conversation

PerplexDaniel
Copy link
Contributor

@PerplexDaniel PerplexDaniel commented Feb 17, 2020

@nielslyngsoe Seperate branch this time, probably easier to check. This is a small change which adds a DisplayName property to the ContentVariantDisplay 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 event EditorModelEventManager.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

@nielslyngsoe nielslyngsoe added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Feb 17, 2020
@nielslyngsoe
Copy link
Member

Still unsure whether we like to have this DisplayName located here. But I think it makes good sense to have it originating from BackEnd. It could be useful for validation messages as well.

I will merge it for now, and we will see if we need to change later.

@nielslyngsoe nielslyngsoe merged commit 12bb2a4 into umbraco:v8/feature/AB4550-segments-ui-variant-picker Feb 18, 2020
@umbrabot umbrabot removed the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants