You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using datetime type headers in the table. columns leads to column widths being set to 0.
Expected behavior
Column widths are left as default if they're assigned to 0 and/or a warning is raised to tell the user that they should parse the header objects to strings.
Should also clarify in docs that only strings/rich-text should be used in all non-data elements.
The text was updated successfully, but these errors were encountered:
The default constructor {'strings_to_numbers': True} means that even strings in index columns might also be converted to numbers by XlsxWriter. As such, auto_width needs to take into account number of digits in numbers. Alternatively, we could try switching this to False and making it clear that users should pass strings to these columns.
Above issue still stands for heading types - warning might be best
Describe the bug
Using datetime type headers in the table. columns leads to column widths being set to 0.
Expected behavior
Column widths are left as default if they're assigned to 0 and/or a warning is raised to tell the user that they should parse the header objects to strings.
Should also clarify in docs that only strings/rich-text should be used in all non-data elements.
The text was updated successfully, but these errors were encountered: