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

Wrong default value for category end date #179

Closed
yankedev opened this issue Sep 1, 2016 · 0 comments
Closed

Wrong default value for category end date #179

yankedev opened this issue Sep 1, 2016 · 0 comments
Labels
bug

Comments

@yankedev
Copy link
Contributor

yankedev commented Sep 1, 2016

Default value of validity-end-date field for a new Category should be equal to the event begin date.

Current behavior sets validity-end-date field to now.

If the event begin date changes, category validity-end-date should be changed too (but only if it has not been changed): this behavior works thanks to the watch-obj property of the dateRange directive. This directive should remain untouched
@yankedev yankedev added the bug label Sep 1, 2016
yankedev added a commit that referenced this issue Sep 1, 2016
@yankedev
Isuue #179: fix new category end date
60fb485
yankedev added a commit that referenced this issue Sep 1, 2016
@yankedev
Isuue #179: fhandle the case when endDate is undefined
1f9b311
yankedev added a commit that referenced this issue Sep 1, 2016
@yankedev
Isuue #179: handle the case when endDate is undefined
86b7380
syjer pushed a commit that referenced this issue Sep 2, 2016
@yankedev @syjer
Calendar fix (#183)
3923391 
* Isuue #179: fix new category end date

* Isuue #179: fhandle the case when endDate is undefined

* Isuue #179: handle the case when endDate is undefined
@ceeedevops ceeedevops mentioned this issue Jan 21, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cbellone @yankedev