Closed calvinclaus closed 8 years ago
Overall looks pretty good, although the indentation seems a bit odd to me personally.
What do you think about the name onClick
. After I implemented it, I thought onDayClick
would fit better? Thoughts?
Summing up:
onDayClick
CalendarDay
a class and pass this
as target
eventData
prop to CalendarDay
and pass this eventData
to onDayClick
[Postponed, waiting for @dptoot]So we would end up with: onDayClick(target, eventData, day)
Good point - onClick
is probably too vague.
eventData
may or may not be necessary actually because the click is happening on the background of a day and not a specific event. Personally I don't care much about that, but maybe @dptoot has a suggestion
Okay. So far so good 🔥 . Let me know if the changes work for you.
Can't a man watch the euros in peace around here? :) sorry for the silence guys. I will review this tomorrow and push it out
Haha thanks @dptoot
Looks pretty good overall. If you can make the changes I suggested and update docs and the demo I would appreciate it. Nice work.
I think this should be ready. Let me know if you want me to rebase this to a sinlge commit.
Looks good guys. Nice addition.
Released in version 0.3.0
Thanks @calvinclaus!
This is a WIP for #21.
I added an
onClick(target, day)
property toEventCalendar
that is passed down toCalendarDay
. It is called when a user clicks on any day in the calendar. If the user clicks on an event directly, theonClick
function is not called, as I added a stopPropagation for theonEventClick
event inCalendarEvent
.WIP I couldn't figure out an easy way to pass a meaningful
target
property toonClick
. At the moment I am just passing the string'day'
. I saw that inCalendarEvent
you are passingthis
, but we cannot do that inCalendarDay
as long as its a functional component. Please let me know how you would like this issue to be resolved.Other In case you like this addition, I am happy to make the changes to README.md, before this is merged.