Setting resourceAreaHeaderContent overrides the value of headerContent is resource columns

[tn-bouvet]

Reduced Test Case

https://stackblitz.com/edit/github-6b7aj5?file=src/index.jsx

Do you understand that if a reduced test case is not provided, we will intentionally delay triaging of your ticket?

• I understand

Which connector are you using (React/Angular/etc)?

React

Bug Description

See stackblitz project. When resourceAreaHeaderContent is provided, the calendar overwrites the headerContent in the resourceAreaColumns prop.

Also, while the docs state that the default resource area header should be "Resources", no such header appears as long as resourceAreaColumns are defined.

I have checked without the React connector, and this seems to work in that case. See codepen.

Desired outcome (taken without react connector):

Result when resourceAreaHeaderContent is provided:

Result when resourceAreaHeaderContent is not provided:

[lukas-siarny]

The cellContent with resourceAreaColumns also dosen't work correctly. It works when you return a string, but when you return JSX it renders nothing

I just added cellContent to the test case above:
This doesn't work:

          resourceAreaColumns={[
            { field: 'num', headerContent: () => 'Number' },
            { field: 'name', headerContent: 'Name', cellContent: () => <span>'cellContent'</span> },
          ]}

This works:

          resourceAreaColumns={[
            { field: 'num', headerContent: () => 'Number' },
            { field: 'name', headerContent: 'Name', cellContent: () => 'cellContent' },
          ]}

[acerix]

Thanks, I can confirme this is a bug specfic to React.

Since resourceAreaHeaderContent is getting called for each header, as a workaround, you can add a counter and return the correct header content like this:

https://stackblitz.com/edit/github-6b7aj5-sgfkgx?file=src%2FDemoApp.jsx

[arshaw]

Thanks for this bug report. I'll fix it and release it in a minor release before the end of next week (Jan 27). Sorry for the troubles.

[arshaw]

This is fixed in v6.1.0!

• blog post: https://fullcalendar.io/blog/2023/01/multimonth-and-more
• github release: https://github.com/fullcalendar/fullcalendar/releases/tag/v6.1.0
• updated repro: https://stackblitz.com/edit/github-6b7aj5-nebprp?file=package.json