Warn if you have optimization on and write rows in the wrong order

[neilb]

If a workbook has optimization enabled, you could generate a warning if rows are written to out of order.

On a related note, I plan to submit a PR to update the documentation in a couple of places :-)
I'll do that as one of my Hacktoberfest PRs!

Cheers,
Neil

[jmcnamara]

If a workbook has optimization enabled, you could generate a warning if rows are written to out of order.

Perhaps. This behaviour is documented and I've had very few issues reported around this. The documentation on this "feature" could probably be improved a bit. I did that recently for the Python version of the module.

I'll keep it in mind though.

On a related note, I plan to submit a PR to update the documentation in a couple of places :-)
I'll do that as one of my Hacktoberfest PRs!

Yes. Please do. :-)

[neilb]

This behaviour is documented and I've had very few issues reported around this

Please consider this one such report :-)

We switched from XLS to XLSX, and I didn't notice at the time that some headers (easy to calculate after processing all rows) were no longer showing. They were all merged headers, which slightly led me down the wrong path. I read various bits of the doc, and spent well over an hour trying to work out what the heck was going on.

Eventually I trawled through the close github issues, and that's where I found the answer.