Conversation
This adds support for a new `timeofday` input field in the issue template that allows to capture an expressed preference for when a session ought to be scheduled: morning, afternoon, evening, or no preference. The parsing logic makes it possible to complete the option labels for a given event, e.g., to say "Afternoon slot (25 March)". The validation logic reports a `times` warning when a meeting is scheduled at an inappropriate time. For example when a session that ought to take place in the morning is scheduled in the afternoon. - Morning is taken to mean "before or at 12:00". - Afternoon is taken to mean "at or after 13:00 and before 19:00". - Evening is taken to mean "at or after 19:00" Scheduler takes the field into account to choose an appropriate time. It relaxes the constraint once other non-critical constraints have been relaxed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addresses #298.
This adds support for a new
timeofdayinput field in the issue template that allows to capture an expressed preference for when a session ought to be scheduled: morning, afternoon, evening, or no preference.The parsing logic makes it possible to complete the option labels for a given event, e.g., to say "Afternoon slot (25 March)". The validation logic reports a
timeswarning when a meeting is scheduled at an inappropriate time. For example when a session that ought to take place in the morning is scheduled in the afternoon.Scheduler takes the field into account to choose an appropriate time. It relaxes the constraint once other non-critical constraints have been relaxed.