Our blazing fast Grid component built with pure JavaScript


Post by ashupp »

Hello,

i am encountering an issue when using grouping on grid or scheduler (pro).
It seems the group counts in headers are wrong when using grouping.
The group counts are changing when sorting ascending / decending.

Also to reproduce / visible on Examples:

Grid:
https://www.bryntum.com/examples/grid/groupsummary/

  • Open Example
  • Scroll to bottom and see Group header "Washington 0" instead of expected 1.
  • Scroll up and Sort Column "City" descending and see Group header "Washington" changes to "Washington 1" which is correct.
  • Scroll again to bottom and see Group header "Barcelona 4" - which was 5 before sorting.

It seems like the last element on end of table has count -1?

Scheduler:
https://www.bryntum.com/examples/examples-scheduler/groupsummary/

  • Open Example
  • Scroll to bottom and see Group header "Testers 4" instead of expected 5.

Same behaviour as above - also when sorting (tough not possible in the example but tested in own code)

Actually this is critical for me. I can not use a grid or calendar showing wrong values.

I licensed scheduler pro and grid - and this is acutally the 5th bug i reported within 10 days using the librarys and i start being concerned what to expect next.

In another thread i was asking for grid to grid drag and drop support. I could imagine support on that topic could be a kind of compensation for the times i had to spent on tracking down the bugs and reporting.

Let me know what you think about that. I really like the grid and scheduler with its design an fuctionality but honestly i am currently close to the point where i have to stop this journey and go two steps back.

Edit:
I just found out the issue happens when using groupSummary: true

Thank you and best regards, Alex


Post by arcady »

That looks like a bug. Thank you for the feedback!
Here is a ticket for the grid issue: https://github.com/bryntum/support/issues/1782
And in case it's smth different (most probably fixing grid will resolve it but anyway) a separate scheduler ticket: https://github.com/bryntum/support/issues/1783


Post by arcady »

Fixed version can be found in the next nightly build in the customerzone. Thank you for the feedback!


Post Reply