Permalink
Browse files

Do not render a <div> surrounding Weekday

  • Loading branch information...
gpbl committed Nov 3, 2015
1 parent aa9e2e6 commit 0164a38f651771c00d3b4949898937d2013c7ddd
Showing with 1 addition and 5 deletions.
  1. +1 −5 src/DayPicker.js
View
@@ -306,11 +306,7 @@ class DayPicker extends Component {
</div>
);
}
return (
<div>
{ days }
</div>
);
return days;
}
renderWeeksInMonth(month) {

5 comments on commit 0164a38

@nkbt

This comment has been minimized.

Show comment
Hide comment
@nkbt

nkbt Nov 11, 2015

That sort of broke my styling, but was an easy fix...

nkbt replied Nov 11, 2015

That sort of broke my styling, but was an easy fix...

@gpbl

This comment has been minimized.

Show comment
Hide comment
@gpbl

gpbl Nov 11, 2015

Owner

I'm sorry for that 😓! How did it broke it?

Owner

gpbl replied Nov 11, 2015

I'm sorry for that 😓! How did it broke it?

@nkbt

This comment has been minimized.

Show comment
Hide comment
@nkbt

nkbt Nov 11, 2015

No problem at all, I had a style .DayPicker-Weekdays > div. I reckon it was copied from DayPicker.css directly.

was easy to spot and fix.

I also used day-picker/lib/Utils, but that was another super easy fix. Anyway it was not "officially" exposed, so... =)

nkbt replied Nov 11, 2015

No problem at all, I had a style .DayPicker-Weekdays > div. I reckon it was copied from DayPicker.css directly.

was easy to spot and fix.

I also used day-picker/lib/Utils, but that was another super easy fix. Anyway it was not "officially" exposed, so... =)

@gpbl

This comment has been minimized.

Show comment
Hide comment
@gpbl

gpbl Nov 11, 2015

Owner

Oh well now I understand the reason of that div 😱 Also, having moved the old .scss style to a normal .css style, I couldn't see the error. I'm going to revert this change (see #82). Sorry for the hassle!

Owner

gpbl replied Nov 11, 2015

Oh well now I understand the reason of that div 😱 Also, having moved the old .scss style to a normal .css style, I couldn't see the error. I'm going to revert this change (see #82). Sorry for the hassle!

@nkbt

This comment has been minimized.

Show comment
Hide comment
@nkbt

nkbt replied Nov 11, 2015

👌

Please sign in to comment.