Skip to content

float64's that are NaN cause corrupt .xlsm file #119

@sanoanalytics

Description

@sanoanalytics

I stumbled upon a bug. If you pass a float64 to SetCellValue() and it is NaN, it causes a corrupt .xlsm file. I simply used math.IsNaN() to check prior to SetCellValue() and that the solved problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions