Conversation
when the last session of a day crossed a date barrier in the user-local time (but not the event time), the schedule still omitted the rest of the day when displaying in event time, resulting in e.g. a 7:30pm-8:00pm session in event time showing as cross-date (but still only 30 minute long), because the remaining date timeslices were omitted, even though this should have only happened in user time
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
2 participants
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.
Progress
Problems
customElement: truewould cause all components to have inlined css)pretalx-schedule.jsnow needs to be loaded withtype=modulebecause of theexport defaulton the last line, which would break all existing pretalx schedules out there, I think?