-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle and updates worksheet dimensions automatically #1200
Comments
Thanks for your feedback. Please provide your input file attachment without confidential info if you can. |
This library doesn't handle and updates worksheet dimensions automatically when saving the spreadsheet currently. I'll consider adding this feature support later. You can calculate it by the total columns and rows of the worksheet. |
Thanks, can i see this feature in the next version? |
Sorry, this feature won't be released in the next version. You can calculate it by the total columns and rows of the worksheet. |
I used "excel" to add a line at the end of the workbook and save it. It's work, and both office and WPS can preview it.
But when I use Node to read this file, I can't read the newly added content. The NODE found an attribute "! Ref". This area is still the old attribute
It is worth mentioning that when I found that the NODE could not read the information normally, I saved it again with "office / WPS". It is found that the node can be read normally.
So I guess "! Ref" represents the content range of EXECL. Whether to update the relevant content when it is not saved. Unfortunately, my ability is not enough to read the source code and modify it.
My Go Code:
My Node Code:
Describe the results you received:
![image](https://user-images.githubusercontent.com/20927608/162134367-d345451b-23ae-41d7-a048-0aa06c03a782.png)
Describe the results you expected:
'!ref': 'A2:B2',
Go Environment:
go version go1.15.6 darwin/amd64
github.com/xuri/excelize/v2 v2.5.0
Node Environment:
v16.14.2
xlsx: "^0.18.5"
Thanks
The text was updated successfully, but these errors were encountered: