Skip to content
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

Push to PHP 7.2 #159

Merged
merged 29 commits into from
Mar 7, 2019
Merged

Push to PHP 7.2 #159

merged 29 commits into from
Mar 7, 2019

Conversation

tvdijen
Copy link
Member

@tvdijen tvdijen commented Jan 22, 2019

Minimum version is PHP 7.2

Upgrades PHPunit to 7.x

@coveralls
Copy link

coveralls commented Jan 22, 2019

Coverage Status

Coverage decreased (-0.1%) to 66.557% when pulling 49d39e8 on php71 into 7d7fd4d on master.

@tvdijen
Copy link
Member Author

tvdijen commented Jan 22, 2019

HHVM is now definitely broken because PHPcpd relies on Symfony4..

@tvdijen tvdijen changed the title Push to PHP 7.1 Push to PHP 7.2 Jan 23, 2019
Copy link
Member

@jaimeperez jaimeperez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent job! I've noticed a couple of issues with properties losing their null default, but other than that, looks good to me! 👍 (I should probably admit that I haven't reviewed everything in detail though, due to the size of the PR).

src/SAML2/AuthnRequest.php Outdated Show resolved Hide resolved
src/SAML2/XML/md/KeyDescriptor.php Outdated Show resolved Hide resolved
@tvdijen
Copy link
Member Author

tvdijen commented Jan 23, 2019

Psalm really doesn't like those assertions... And neither do I..
What a mess to get the tests to pass again

@jaimeperez
Copy link
Member

It makes sense, after all. It's not checking the source code for the webmozart/assert library, so it doesn't have any possible way to know that after the assertion, the variable is guaranteed to have a value.

In any case, I'd say psalm is serving its purpose very well... 😄

@tvdijen
Copy link
Member Author

tvdijen commented Jan 24, 2019

Can we specifically include the webmozart source to prevent these kind of issues in the future?

@jaimeperez
Copy link
Member

If it passes the psalm tests, that could be a good idea, yes. I was already thinking about it, but I'm not sure it would pass. Also, if it breaks at some point, our builds would break with nothing we can do to fix them...

@tvdijen
Copy link
Member Author

tvdijen commented Jan 24, 2019

Changes to the webmozart library are minimal, looking at their history.. I'd say we go for it.
Worst case scenario, we have to suppress (or cast to info) specific errors on a per-file basis.

Given the nature of the xmlseclibs library, we may want to include that one too. Also not a library that has too many changes.

@jaimeperez
Copy link
Member

xmlseclibs is failing hard nowadays. I submitted a PR to fix the issues, but would need that merged (and psalm integrated as part of the build process as well) before we can include it in our own tests.

@tvdijen

This comment has been minimized.

@jaimeperez

This comment has been minimized.

@tvdijen
Copy link
Member Author

tvdijen commented Jan 25, 2019

How do you feel about writing our own Stub-files for XMLSecLibs and Webmozart? As an alternative to including them in the Psalm-config. This is also really useful for SSP, for PHP-libs like ldap and radius..

@tvdijen
Copy link
Member Author

tvdijen commented Jan 26, 2019

OK, stubs are nice for php-libs, not for the webmozart asserts.
Also, including the vendor/webmozart/assert dir to the project didn't have the expected result

@tvdijen tvdijen dismissed jaimeperez’s stale review March 7, 2019 14:07

Issues were addressed

Since we require PHP 7.2, we can now also move to PhpUnit 8.

Only some deprecation warnings needed attention.
@tvdijen tvdijen merged commit 81edb90 into master Mar 7, 2019
@tvdijen tvdijen deleted the php71 branch November 6, 2019 13:49
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants