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
Cell property HasComment is True but GetComment() returns empty object #1920
Comments
I have the same problem here, could you please merge the PR? @NickNack2020 😃 |
@tiagoalmeidadarosa a maintainer like @jahav has to merge the associated PR. I want to be an active contributor to ClosedXML and have submitted multiple PRs, but I gave up and stopped contributing when PRs are not being merged or responded too. As you can see this PR has been open for over 6 months. |
It was stated in a past issue that @jahav is focused on core technical debt more so then bug fixes see (#2161) I don't disagree with the fact that his time can best be spent here, but then I wish we were more willing to accept community bug fixes from others. Getting others engaged in the project is what will help build up more knowledge and sustainable resources to keep the project health long term, but for now it seems like we are not focused on that. |
Do you want to request a feature or report a bug?
Did you test against the latest CI build?
Version of ClosedXML
0.95.0
0.97.0
0.97.1 - preview
What is the current behavior?
I try to export google sheet with Notes as xlsx file.
And exported file looks like this in Excel. All Notes have been changed to Comments.
But when I try read comment in code the next behavior is a bit unexpected.
Also if I try resave the file all comments just disappear:
What is the expected behavior or new feature?
I'd like to read comments like in Excel file.
Is this a regression from the previous version?
I've checked this code on version 0.95.0 The problem is reproduced too.
Reproducibility
Code to reproduce problem:
I'm using .Net 6. Test file has been attached to issue.
Test ClosedXML.xlsx
The text was updated successfully, but these errors were encountered: