-
Notifications
You must be signed in to change notification settings - Fork 203
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
EZP-31123: Fixed strict types-related casting issues #2843
Merged
Merged
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
7 tasks
5 tasks
alongosz
changed the title
Fixed strict types-related casting issues
EZP-31123: Fixed strict types-related casting issues
Nov 13, 2019
alongosz
force-pushed
the
fix-misc-type-cast-errors
branch
from
November 13, 2019 11:11
a867575
to
21db157
Compare
\eZ\Publish\Core\Persistence\Legacy\Content\Gateway\DoctrineDatabase: * ensured StorageFieldValue::sortKeyString is string prior to calling mb_substr. * ensured listVersionNumbers always returns an array of integers as the internal result set type depends on a DBMS driver.
Ensured Location\Handler::copySubtree casts raw database values to integer prior passing them to Content\Handler::copy (and to the underlying Content Gateway).
alongosz
force-pushed
the
fix-misc-type-cast-errors
branch
from
January 20, 2020 09:27
21db157
to
548220c
Compare
Let's proceed with review and QA to unblock #2845. Further fixes will be added as a follow-up (if needed). |
alongosz
requested review from
mikadamczyk,
webhdx,
adamwojs,
michal-myszka,
ViniTou and
Nattfarinn
January 20, 2020 09:47
ViniTou
approved these changes
Jan 21, 2020
adamwojs
approved these changes
Jan 21, 2020
michal-myszka
approved these changes
Jan 23, 2020
mikadamczyk
approved these changes
Jan 23, 2020
katarzynazawada
approved these changes
Jan 24, 2020
Could you merge it up? |
Merged via 32a73c2. |
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.
7.5.x
for eZ Platform 2.5.x LTS.This PR is a cumulative fix for strict types casting issues found while working on EZP-30921 and EZP-31088 (and possibly others).
(fixed via EZP-30754: Fixed handling always available flag for ContentInfo update #2850)\eZ\Publish\Core\Persistence\Legacy\Content\Mapper::extractContentInfoFromRow
:eZ\Publish\SPI\Persistence\Content\ContentInfo::$alwaysAvailable
should be Boolean instead of Integer.QA
TODO:
$ composer fix-cs
).