You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i wonder about the publish workflow naming and concept. should we have a concept that PublishWorkflowCheckerInterface can be chained, having isPublished return true|false|null ?
also i wonder if PublishWorkflowChecker should be called TimebasedPublishChecker or something, and the PublishWorkflowInterface TimebasedWorkflowInterface? we could already now split out the ispublished flag from the timebased and start to have a chain. then it would be easy to add other workflow checkers to the chain, for example based on a user role or whatever people come up with.
The text was updated successfully, but these errors were encountered:
Actually, I wonder also if this shouldn't be broken down into 2 interfaces: PublishableInterface and PublishTimePeriodInterface. Or maybe even, having just looked at Typo3, VisibileInterface and PublishDatesInterface.
yes, i think that would make sense. and then we would start having a PublishCheckerChain running PublishableChecker and PublishDatesChecker that get active if the model implements PublishableInterface resp PublishDatesInterface. hm, i just dropped workflow here, but i think it does make sense to drop it as anyway none of this helps with workflows, only with the binary visibility decision.
i wonder about the publish workflow naming and concept. should we have a concept that PublishWorkflowCheckerInterface can be chained, having isPublished return true|false|null ?
also i wonder if PublishWorkflowChecker should be called TimebasedPublishChecker or something, and the PublishWorkflowInterface TimebasedWorkflowInterface? we could already now split out the ispublished flag from the timebased and start to have a chain. then it would be easy to add other workflow checkers to the chain, for example based on a user role or whatever people come up with.
The text was updated successfully, but these errors were encountered: