Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

make sure user can not set dtend to something earlier than dtstart #245

Open
georgehrke opened this issue Feb 27, 2016 · 3 comments
Open

make sure user can not set dtend to something earlier than dtstart #245

georgehrke opened this issue Feb 27, 2016 · 3 comments
Assignees
@georgehrke
Labels
1 - to develop JS
Milestone
1.5-next

Comments

@georgehrke
Copy link
Contributor

No description provided.

@georgehrke georgehrke added this to the Beta 1 milestone Feb 27, 2016
@georgehrke georgehrke changed the title make sure user can not set dtend to something earlier than distart make sure user can not set dtend to something earlier than dtstart Feb 27, 2016
@georgehrke
Copy link
Contributor Author

heads up: dtstart and dtend may have different timezones
introduce some service that utilizes ICAL

@georgehrke
Copy link
Contributor Author

important: What if the ends timezone is earlier than the starts timezone

@georgehrke georgehrke modified the milestones: Beta 1, RC 1 Mar 3, 2016
@georgehrke georgehrke self-assigned this Mar 6, 2016
@georgehrke
Copy link
Contributor Author

I'm not happy about this but we have to move this to 1.1

The good thing: fullcalendar will still display the event, if event if ends before it starts, so it's not "lost"

@georgehrke georgehrke modified the milestones: Version 1.1, RC 1 Mar 6, 2016
@georgehrke georgehrke modified the milestones: 1.2-next, 1.1-current Apr 10, 2016
@georgehrke georgehrke modified the milestones: 1.3-next, 1.2-current May 12, 2016
@georgehrke georgehrke modified the milestones: 1.3-current, 1.4-next (ownCloud 9.1) Jul 6, 2016
@georgehrke georgehrke mentioned this issue Aug 4, 2016
Closed
@georgehrke georgehrke modified the milestones: 1.5-next, 1.4-current Aug 14, 2016
@raimund-schluessler raimund-schluessler mentioned this issue Aug 22, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@georgehrke georgehrke

Labels
1 - to develop JS
Projects
None yet
Milestone
1.5-next
Development

No branches or pull requests
1 participant
@georgehrke