Our pure JavaScript Scheduler component


Post by bizzcoo »

Hello,

I am having some trouble getting the summary and group summary to work.

I use Scheduler Pro 1.0.2.

When adding the summary feature, a row is added at the bottom of the scheduler, but the row just has empty cells.

When adding the group summary feature, an error is thrown: "Uncaught (in promise) TypeError: _0x24bae3.recurringEvents is undefined"

Since there is no example for summaries specifically for Scheduler Pro, I have taken inspiration from https://www.bryntum.com/examples/examples-scheduler/summary/ and https://www.bryntum.com/examples/examples-scheduler/groupsummary/.

A test case is attached. However, the same happens when adding this code snippet to an existing Scheduler Pro demo (https://www.bryntum.com/examples/scheduler-pro/grouping/):

summary: {
    renderer: ({ events }) => {
        return events.length || 'nothing';
    }
},
groupSummary: {
    summaries: [
        {
            label: 'Events',
            renderer: ({ events }) => {
                return events.length || 'nothing';
            }
        }
    ]
}

What am I doing wrong here?
Are summaries (summary, groupSummary, summaryRenderer/summaries for columns) configured differently for Scheduler Pro?

Attachments
schdulerpro-summary-test.zip
(1.44 KiB) Downloaded 96 times

Post by mats »

Try using latest nightly Pro build from the customer zone? I have a feeling this is already fixed there.


Post by bizzcoo »

Thank you for the quick response.

Yes, using the nightly build schedulerpro-2020-09-21-next solved the groupSummary and the column summary issue.

The summary row is still empty though, (see image below, I highlighted one of the cells in the footer that is added when the summary feature is added to the scheduler, in which I would assume the summary result to be).

expected-summary.png
expected-summary.png (96.93 KiB) Viewed 1301 times

I have also tried the below config without any success:

summary: {
          summaries: [
            {
              label: 'Total',
              renderer: ({ events }) => {
                return events.length || 'nothing';
              }
            }
          ]
        }

Post by mats »

That's a bug yes, we'll get it fixed right away: https://github.com/bryntum/support/issues/1549


Post by bizzcoo »

Awesome, thanks!


Post Reply