@syncfusion/[email protected] contains pdf-export.js with the following function signature:
PdfExport.prototype.processAggregates = function (sRows, pdfGrid, border, font, brush, backgroundBrush, isCaption, captionRow, groupIndex, isGroupedFooter, isAggregate)
Note the last argument isAggregate.
However, the source file in GitHub does not match:
private processAggregates(
sRows: Row<AggregateColumnModel>[], pdfGrid: PdfGrid, border: PdfBorders, font: PdfFont,
brush: PdfSolidBrush, backgroundBrush: PdfSolidBrush, isCaption: boolean,
captionRow?: PdfGridRow, groupIndex?: number, isGroupedFooter?: boolean
)
Note the missing isAggregate argument.
This affects me, because I'm trying to debug a regression in the pdf export when updating from version 19.2 to the latest 19.3.
What is the reason for this discrepancy?
Thanks.
Attached is a demo of the regression caused by this isAggregate argument. The group footer templates are no longer exported to PDF, nor are the other aggregate columns of the final footer row. It seems there are two bugs with respect to isAggregate:
1) isAggregate is requiring to be falsey in order to export aggregate columns, but for final footer it's true so it's not getting rendered.
2) isAggregated is requiring to be true in order to render footer and group footer templates, but for group footers is undefined (falsey) so it's not getting rendered.
And then with regards to my first comment above, why is this new code not in GitHub?
Thanks.
Similarly, it looks like version 19.3.54 was just released, and the git commit has no source code changes. The release notes clearly indicates source code was changed.
https://ej2.syncfusion.com/vue/documentation/release-notes/19.3.54/?type=all#grid
Hi, can you please explain why the GitHub repo source code doesn't match the npm packages? Thanks.
Hi Pavithra,
Thanks very much for resolving the GitHub issue. Yes I've been debugging using the source code in the npm packages, but having GitHub commits for each release will help a lot when there is a regression to be able to diff and identify what code change may have caused it.
Take care.
Hi I see version 56 came out, but the source code in Github still doesn't look right. The version 56 commit only contains changelogs, and even the changelog diffs are blank, except that version 55 was removed and 56 added.
-## 19.3.55 (2021-11-23)
+## 19.3.56 (2021-12-02)
Thanks very much Rajapandi.
I just checked your Github commit, and they haven't included any code changing since the first release of 19.4 in December.
Hi Bill,
Thanks for your patience,
We have resolved your reported issue at our end and also Git repo has been updated to the latest version. So, kindly check again.
Please let us know if you have any concerns.
Regards,
Gokul
Thank you Gokul.