Closed kellyredd closed 5 months ago
Upon further investigation it looks like the resource
prop is what is needed, not the accessors
prop. PR will reflect this change.
:tada: This issue has been resolved in version 1.13.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Clear and concise description of the problem
As a developer I need to make decisions about how I want to render my custom
DayColumnWrapper
component. I need to be able to access info about theResource
that each column falls under in order to apply conditional styling. Having access to the Calendar'sAccessors
would provide this.Suggested solution
https://github.com/jquense/react-big-calendar/blob/621b8f1202b6a1e11dda77095c0cbec4c710fa14/src/DayColumn.js
Passing the destructured
accessor
prop from L110 into theDayColumnWrapperComponent
on L129 would solve this.Alternative
No response
Additional context
No response
Validations
Would you like to open a PR for this feature?