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.

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

Entries that span multiple days cannot access end date #6

Closed
fvaldes33 opened this issue Jan 29, 2019 · 5 comments
Closed

Entries that span multiple days cannot access end date #6

fvaldes33 opened this issue Jan 29, 2019 · 5 comments

Comments

@fvaldes33
Copy link
Contributor

@janmeeus - Opening a new ticket for these other issues

When adding a yearly occurrence that lasts several days (e.g. 20-02-2019 to 24-02-2019), I can only display the startDate of the next occurrence ({{ event.calendarizeHandle.next }}), but not the endDate of the next occurrence.

@fvaldes33
Copy link
Contributor Author

Suggestion would be to add a new method nextEnd or nextRange for example that will return the end date or an object with both the start and end date.

The nextRange method would return an object with both the start and end date and used like below:

entry.calendarizeHandle.nextRange.startDate.format('format')
entry.calendarizeHandle.nextRange.endDate.format('format')

Otherwise, I could change the next functionality to work like above but that would not be backwards compatible.

@robarov
Copy link

robarov commented Feb 13, 2019

Maybe something like this?

entry.calendarizeHandle.next.startDate|date('Y-m-d')
entry.calendarizeHandle.next.endDate|date('Y-m-d')

Of course, it .next should always return the starting date, even if there is no endDate.

@havardlj
Copy link

This currently has me looking for an alternative to Calendarize, too bad, cause it's its only shortcoming for my use

@havardlj
Copy link

Is there any way of disabling the repeats-part of the calendarize field until this is implemented?

fvaldes33 added a commit that referenced this issue May 2, 2019
Updated README to show new changes.
@fvaldes33
Copy link
Contributor Author

@robarov @havardlj @janmeeus

This has been added in 1.2.12. Take a look at the readme to see how it was implemented.

Commit: 19f4782

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants