From 7ead582cd1d4e80342d181a1a0aa0793731692ec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niels=20Lyngs=C3=B8?= Date: Mon, 15 May 2023 10:47:20 +0200 Subject: [PATCH] remove comment --- .../property-settings/property-settings-modal.element.ts | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/Umbraco.Web.UI.Client/src/backoffice/core/modals/property-settings/property-settings-modal.element.ts b/src/Umbraco.Web.UI.Client/src/backoffice/core/modals/property-settings/property-settings-modal.element.ts index 7913737436..741590f8cf 100644 --- a/src/Umbraco.Web.UI.Client/src/backoffice/core/modals/property-settings/property-settings-modal.element.ts +++ b/src/Umbraco.Web.UI.Client/src/backoffice/core/modals/property-settings/property-settings-modal.element.ts @@ -195,11 +195,6 @@ export class UmbPropertySettingsModalElement extends UmbModalBaseElement< }); } - /* TODO: - From Github comment: We should not re-generate the alias when it gets locked again. - Generally the auto generation is not determined by the lock, but wether it has been changed or saved. - The experience in existing backoffice is: we only generate an alias when a property is new, once it has been saved it should never change unless the user actively does so. - On new properties, the alias auto-generates until the user has made a change to it. */ #onToggleAliasLock() { this._aliasLocked = !this._aliasLocked;