Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #112
This PR was originally #154 , but I ended up making a mess of git (multiple reorders + squashing after reorder is hard 😞 ). So go look there for comments. However here is the original PR message:
This PR adds in the ability to specify
navPrev
, andnavNext
to DayPicker incase they want to override the default SVGs that come bundled with react-dates (e.g.ChevronUp
,ChevronDown
,LeftArrow
, andRightArrow
).If
navPrev
, ornavNext
aren't specified then DayPicker will fall back to the current behavior of:for the previous button, and:
for the next button.
I also tried to make this work as much with existing code as possible. As such even with custom icons the class names:
DayPicker__nav--prev
, andDayPicker__nav--next
are still rendered even with custom icons. If you really want to target something inside of your custom icon, you can always tag class names/ids onto the props you pass in. E.g.: