Jilani Syed
Jilani Syed
@schungx you raise a very valid point, but i think this library is not implemented in that way. The spreadsheet is decoded into memory props which is then manipulated as...
@schungx Yes but take in the use case of just reading the excel range into memory as vec of strings. For that it would be waste of resource to load...
@MathNya, i felt `lazy_read(path)` is lacking sufficient documentation for exact use case. I was using `book.get_sheet(&0). unwrap()` and getting error. Also, once the sheet is loaded that would mean things...
I think #158 may be a suitable starting point for the issue.
> Oh, sorry. We have released the latest version, but just now we realized that it is not supported here. We will fix it soon. @MathNya, kindly also update github...
@MathNya if you wish to include this, you can create a feature branch. This will facilitate development of the necessary feature which could be merged on suitable time.
@schungx, can you please share minimal code and test excel for duplication.
@schungx, there is a `_FilterDatabase` in original file (`xxx.xlsx`) the same is written to output file (`output.xlsx`) as
@schungx, the mystery of `_FilterDatabase` is now solved, now it needs to be investigated why the `definedName` element name is placed in the background in that range?
@MathNya can you add milestone for each of the points mentioned in original issue