-
Notifications
You must be signed in to change notification settings - Fork 72
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
Psalm patrol #206
Psalm patrol #206
Conversation
Failing tests are not connected to the changes made but connected to psalm. Psalm requires https://github.com/composer/package-versions-deprecated which replaces https://github.com/Ocramius/PackageVersions. This is causing a missing dependency because the original one does not get installed anymore. Im not sure how to solve this and if this should be part of this PR. Anyhow should package replacing via composer be part of this package knowledge? |
@DanielBadura wouldn't worry too much about it: I think the CI pipeline needs a bit of an overhaul before moving forward. Specifically, in order to maintain things more efficiently, we need:
This patch should mostly be fine as-is |
https://www.youtube.com/watch?v=DzUCC9pfoNw Are workflows already enabled? |
Now it should be ready for review @Ocramius 👍 |
97ec7b9
to
0ad00d2
Compare
Rebased to get the I could not figure out how to test this case since |
@DanielBadura about that last bit, I'm wondering if we can replace it with an assertion? |
@Ocramius im not quite sure if i understood you correctly. I pushed some changes. With this we dont loose the |
Let's re-discuss this one after a rebase on top of #210 (and discussion there first!) |
Since #210 is merged now i will rebase this PR the next days |
2d24e16
to
d5f5993
Compare
So this is rebased now. Still getting the error mentioned before:
As this is targeting v3.0.0 now it would be feasible to drop composer 1 support and with it get rid of PackageVersion and get the package version via composer 2 api. WDYT @Ocramius ? And if so - extra PR for dropping composer v1 or smash it into this one? :D |
Sounds good to me. Beware that we still need #218 for that to work correctly, since I would suggest reviewing that, and then we do yet another (sorry!) rebase here to squish out |
No problem at all :) |
@DanielBadura this can now be rebased |
Alright, thanks for the notification 👍 |
… Param::type to be string
…ent the tool itself says its not installed which is true
a05e169
to
c81fef8
Compare
…ersions: with this composer 1 support is dropped, replace the usage of version
@Ocramius PR is rebased and PackageVersions is out in favor for the composer-runtime-api^2 as discussed above. So with this PR we drop composer 1 support. This PR is from my side finished & ready :) |
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.
Excellent, thanks @DanielBadura!
No description provided.