Add mechanism to specify custom slot start/end times #118
Conversation
This file contains 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
See #100. If the start/end times of a meeting needs to be adjusted for some reason, the actual start/end times may now be specified in the `Meeting` field using `<HH:mm>` next to the time that needs to be modified. For example: - `9:00<8:30>` - `9:00-11:00<10:30>` - `11:00<11:15> - 13:00<12:45>` Validation will reject problematic custom times: - a custom start time that overlaps with a previous slot - a custom end time that overlaps with a next slot - custom times that do not change anything - custom times that make no sense (e.g., because custom start time is later than the custom end time) The custom start/end times are used in the calendar. If a group meets during contiguous slots and custom start/end times are set for the inner slots, the custom start/end times are ignored. For example, the custom times are ignored in `9:00; 11:00<11:15> - 13:00<12:45>; 14:00` because this will map to only one calendar entry from `9:00` to `16:00`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See #100. If the start/end times of a meeting needs to be adjusted for some reason, the actual start/end times may now be specified in the
Meetingfield using<HH:mm>next to the time that needs to be modified.For example:
9:00<8:30>9:00-11:00<10:30>11:00<11:15> - 13:00<12:45>Validation will reject problematic custom times:
The custom start/end times are used in the calendar.
If a group meets during contiguous slots and custom start/end times are set for the inner slots, the custom start/end times are ignored. For example, the custom times are ignored in
9:00; 11:00<11:15> - 13:00<12:45>; 14:00because this will map to only one calendar entry from9:00to16:00.