Place scheduled on sectionQuery, use startDate from schedule. #249
Conversation
| @@ -69,6 +69,7 @@ module.exports = async ({ | |||
| else: '$expires', | |||
| }, | |||
| }, | |||
| scheduled: '$startDate', | |||
There was a problem hiding this comment.
What's this intended to be used for?
There was a problem hiding this comment.
Currently there isn't a field on sectionQuery if the schedule has a startDate set prior to the content published date (why this is a "thing" beats me). This adds one.
There was a problem hiding this comment.
For what purpose? Section query intentionally uses published date to correct certain schedule start dates... in that example, that start date is actually wrong... you shouldn't be able to start content before it's actually published. Nothing in the interface prevents this, per se, hence why section query enforces this
There was a problem hiding this comment.
I don't agree with the idea of putting dates prior to the publish date anywhere.
|
@Shinsina we're going to hold on these changes for now, pending some other options |
Ref: #247