-
Notifications
You must be signed in to change notification settings - Fork 89
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
Calendar week view UI update #435
Calendar week view UI update #435
Conversation
…o98/DES-Website into calendar-week-view-394
…o98/DES-Website into calendar-week-view-394
…o98/DES-Website into calendar-week-view-394
const eventItems = groupCalendar.items | ||
eventItems.forEach((event) => { | ||
const START_DATE = '12:00:00 AM' | ||
const END_DATE = '11:59:59 PM' | ||
|
||
// condition where an event is an "allDay" event fix | ||
if ((event.start.toLocaleTimeString() === START_DATE) && (event.end.toLocaleTimeString() === END_DATE)) { | ||
event.allDay = true | ||
} | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great @johnjovero98 I'm fairly sure this takes into account this fix https://github.com/devedmonton/DES-Website/pull/429/files correct?
This looks pretty awesome to me so far I'm good to merge this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I rebased my branch that includes those changes from PR 429.
This looks great just something to note in the future is that in firefox the "all day" event is not showing so maybe @johnjovero98 could file a bug later with https://github.com/antoniandre/vue-cal-v4/issues. I'm going to merge this and we can deal with it later. |
What issue is this referencing?
#394
Do these code changes work locally and have you tested that they fix the issue yourself?
Does the following command run without warnings or errors?
npm run pr-checks
Have you taken a look at our contributing guidelines?
My node version matches the one suggested when running
nvm use
?demo: