Closed Tux closed 8 years ago
I'm hesitant to document internal implementation details of Spreadsheet::ParseExcel, since they might change in the future (and so then my code would also have to change to retain compatibility, which it can't do if I document it). Are the documented methods is_merged
and get_merged_areas
not sufficient?
I would have used those if I would have found them in the manual.
None of man Spreadsheet::ParseExcel, man Spreadsheet::ParseXLSX, perldoc Spreadsheet::ParseExcel, and perldoc Spreadsheet::ParseXLSX mention any method for merged cells.
See https://github.com/Tux/Spreadsheet-Read/issues/1 for the original report
I would never have found the first without a reference to it in the top-level docs. Maybe a section about merged cells?
https://github.com/Tux/Spreadsheet-Read/commit/4a2683c61f6c28e7a2da3a1fc79368efae124772 works fine.
I added references to the Spreadsheet::ParseExcel documentation in 0f73ea7 - I'm not too interested in maintaining a full copy of the Spreadsheet::ParseExcel docs myself, but hopefully this will make them more discoverable.
I use the global sheet info for the known merged areas:
And the cell attribute information on merged cells
Neither is documented, so I am at risk here.
I'd like to see it documented, so I can use it "safe".