-
Notifications
You must be signed in to change notification settings - Fork 469
refactor: optimize the StyleUtil code #466
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
Conversation
alaahong
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems not mandatory to create a new Class with new Method?
e.g. inline usage is enough
Optional.ofNullable(writeCellStyle.getHidden())
.ifPresent(cellStyle::setHidden);
And meanwhile, even for new Utils, please also provide unit test at same time.
|
We can delete the new utility classes and use internal private methods. |
|
|
All CI fails |
|
fix ci |
psxjoy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something needs to change.
|
What else needs to be done |
alaahong
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why involve new version declaration
psxjoy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If no one has other questions, this PR will merge in 24h.
tisonkun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thanks for your contribution!
Merging ...
Purpose of the pull request
#465
What's changed?
Checklist