From 2baf64597bf56d4774f485f8d03d05a4522713bc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niels=20Lyngs=C3=B8?= Date: Thu, 3 Oct 2024 20:44:33 +0200 Subject: [PATCH] TODO --- .../modals/schedule-modal/document-schedule-modal.element.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/src/Umbraco.Web.UI.Client/src/packages/documents/documents/modals/schedule-modal/document-schedule-modal.element.ts b/src/Umbraco.Web.UI.Client/src/packages/documents/documents/modals/schedule-modal/document-schedule-modal.element.ts index dc850eb0ad..9665b023c0 100644 --- a/src/Umbraco.Web.UI.Client/src/packages/documents/documents/modals/schedule-modal/document-schedule-modal.element.ts +++ b/src/Umbraco.Web.UI.Client/src/packages/documents/documents/modals/schedule-modal/document-schedule-modal.element.ts @@ -51,6 +51,7 @@ export class UmbDocumentScheduleModalElement extends UmbModalBaseElement< } // Only display variants that are relevant to pick from, i.e. variants that are draft or published with pending changes: + // TODO:[NL] I would say we should change this, the act of scheduling should be equivalent to save & publishing. Resulting in content begin saved as part of carrying out the action. (But this requires a update in the workspace.) this._options = this.data?.options.filter( (option) => option.variant && option.variant.state !== UmbDocumentVariantState.NOT_CREATED,