-
Notifications
You must be signed in to change notification settings - Fork 2.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
fix: Allow vAlign and vMerge on Style\Cell to be set to null #2676
Merged
Progi1984
merged 4 commits into
PHPOffice:master
from
SpraxDev:fix/allow-unsetting-cell-style-vmerge-valign
Sep 13, 2024
Merged
fix: Allow vAlign and vMerge on Style\Cell to be set to null #2676
Progi1984
merged 4 commits into
PHPOffice:master
from
SpraxDev:fix/allow-unsetting-cell-style-vmerge-valign
Sep 13, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as outdated.
This comment was marked as outdated.
SpraxDev
changed the title
fix: Allow vAlign and vMerge on Style\Cell to be set to null (#2673)
fix: Allow vAlign and vMerge on Style\Cell to be set to null
Sep 13, 2024
4 tasks
…ce#2673) vAlign and vMerge are initialized as `null` in every style until it is explicitly set. Right now, it is not possible to unset them, after it has been set once. I've added a null-check to skip the validation, based on the default parameter value of `null`, which indicates to me that it once was intended to work like this. I've also fixed the type-hints, which were wrong from the start.
SpraxDev
force-pushed
the
fix/allow-unsetting-cell-style-vmerge-valign
branch
from
September 13, 2024 10:39
6ca43db
to
116be46
Compare
Thanks @Progi1984! I've pushed the test changes |
This should fix the reduction in test coverage because of the new null checking code in the Setter
Progi1984
approved these changes
Sep 13, 2024
@SpraxDev Thanks again for your contribution 🤟 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
vAlign and vMerge are initialized as
null
until it is explicitly set. Right now, it is not possible to unset them, after it has been set once.I've added a null-check to skip the validation, based on the default parameter value of
null
, which indicates to me that it once was intended to work like this.I've also fixed the type-hints, which were wrong from the start.
Fixes #2673
Checklist:
I have updated the documentation to describe the changes(does not apply)