Export column width sets on wrong column, when export to excel

I’m submitting a Bug report

Your Environment

Software	Version(s)
Aurelia	1.31
Aurelia-Slickgrid	3.1.0
TypeScript	3.5.2
Operating System	Windows 10
Node	10.15.3
NPM	6.4.1

Context

I try to setup export to excel, and also set export width for columns.

Expected Behavior

Title should get excel width on 50 point, when exporting.

Current Behavior

Title get default width on “8.43 points” in excel, when exporting. But next column Duration gets 49.29 points, so it seems like width are of one column.

Possible Solution

What I can see when console.log out sheet from customExcelHeader, some extra header styles (mark with red in image) is set before the real ones. Which makes all columns styles be of one column I think.

Code Sample

this.columnDefinitions1 = [
 { id: 'title', name: 'Title', field: 'title', sortable: true, minWidth: 100, exportColumnWidth: 50 },
 { id: 'duration', name: 'Duration (days)', field: 'duration', sortable: true, minWidth: 100 },
 { id: '%', name: '% Complete', field: 'percentComplete', sortable: true, minWidth: 100 },
 { id: 'start', name: 'Start', field: 'start', formatter: Formatters.dateIso },
 { id: 'finish', name: 'Finish', field: 'finish', formatter: Formatters.dateIso },
 { id: 'effort-driven', name: 'Effort Driven', field: 'effortDriven', sortable: true, minWidth: 100 }
];
this.gridOptions1 = {
  enableAutoResize: false,
  enableSorting: true,
  enableExcelExport: true,
  registerExternalResources: [new ExcelExportService()]
};

[ghiscoding]

This is now fixed and released, however please note that you will have to update both Aurelia-Slickgrid v3.3.1 and all Slickgrid-Universal packages to 0.10.2 (there were some TS Typing changes that impacts both side).

[ghiscoding]

@Chibi86 ok I see the problem after testing that in any of the grid, what you were trying to say (I think) is that getGrouping() returns an array and just testing with if (grouping) is not sufficient, instead if should be if (Array.isArray(grouping) && grouping.length) { and after that it works as intended (as shown below).

I’ll push a fix soon, I was about to push a new version this week anyway.