src/Umbraco.Cms.Api.Management/ViewModels/Document/UnpublishDocumentRequestModel.cs

namespace Umbraco.Cms.Api.Management.ViewModels.Document;

public class UnpublishDocumentRequestModel
{
    public ISet<string>? Cultures { get; set; }
}
Publishing in the Management API (#14774) * make CoreScopeProvider available for derived classes * Create publish controller * Add publish functionality * Remove unneeded using * Implement publish for multiple cultures * support multiple cultures in controler * Dont validate properties * Refactor to use PublishingOperationStatus * refactor to use proper publish async methods * Refactor publish logic into own service * Commit some demo code * Add notes about what errors can happen when publishing * Rework ContentPublishingService and introduce explicit Publish and PublishBranch methods in ContentService * Fix merge * Allow the publishing strategy to do its job * Improved check for unsaved changes * Make the old content controller work (as best possible) * Remove SaveAndPublish (SaveAndPublishBranch) from all tests * Proper guards for invalid cultures when publishing * Fix edge cases for property validation and content unpublishing + add unpublishing to ContentPublishingService * Clear out a few TODOs - we'll accept the behavior for now * Unpublish controller * Fix merge * Fix branch publish notifications * Added extra test for publishing unpublished cultures and added FIXME comments for when we fix the state of published cultures in content --------- Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com> Co-authored-by: Zeegaan <nge@umbraco.dk> 2023-11-22 12:52:08 +01:00			`namespace Umbraco.Cms.Api.Management.ViewModels.Document;`

			`public class UnpublishDocumentRequestModel`
			`{`
V14: Unpublish multiple cultures (#15789) * Refactor to accept multiple cultures * Add test * Move logic into service * Remember to complete scope * Move scope creation. * Add test * Close scope on early return * Handle invalid cultures with bad request * Handle valid cultures based on content * Change return type if a culture is required * Refactor content publishing service to have 1 unpublish method * Update tests * Return better error * Scope completes --------- Co-authored-by: Bjarke Berg <mail@bergmania.dk> 2024-02-29 14:38:47 +01:00			`public ISet<string>? Cultures { get; set; }`
Publishing in the Management API (#14774) * make CoreScopeProvider available for derived classes * Create publish controller * Add publish functionality * Remove unneeded using * Implement publish for multiple cultures * support multiple cultures in controler * Dont validate properties * Refactor to use PublishingOperationStatus * refactor to use proper publish async methods * Refactor publish logic into own service * Commit some demo code * Add notes about what errors can happen when publishing * Rework ContentPublishingService and introduce explicit Publish and PublishBranch methods in ContentService * Fix merge * Allow the publishing strategy to do its job * Improved check for unsaved changes * Make the old content controller work (as best possible) * Remove SaveAndPublish (SaveAndPublishBranch) from all tests * Proper guards for invalid cultures when publishing * Fix edge cases for property validation and content unpublishing + add unpublishing to ContentPublishingService * Clear out a few TODOs - we'll accept the behavior for now * Unpublish controller * Fix merge * Fix branch publish notifications * Added extra test for publishing unpublished cultures and added FIXME comments for when we fix the state of published cultures in content --------- Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com> Co-authored-by: Zeegaan <nge@umbraco.dk> 2023-11-22 12:52:08 +01:00			`}`