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

QA Refresh: Upgrade Psalm, Add PHPStan + composer-require-checker #65

Open
wants to merge 7 commits into
base: 1.16.x
Choose a base branch
from

Conversation

gsteel
Copy link
Member

@gsteel gsteel commented Mar 5, 2025

  • Upgrade Psalm to latest, fix or supress issues
    • Everything is now either final in test or @final in src
  • Remove v3 of psr/container from dependencies (It doesn't exist)
  • Add composer-require-checker to local tools and to CI
  • Fix missing, un-declared deps
  • Add a Makefile for running QA and building docs locally
  • Add PHPStan on max level with a small baseline and fix a load of minor issues

@gsteel gsteel added Enhancement New feature or request dependencies Pull requests that update a dependency file QA Quality assurance tasks such as static analysis improvements labels Mar 5, 2025
@gsteel gsteel added this to the 1.16.0 milestone Mar 5, 2025
@gsteel gsteel requested a review from a team March 5, 2025 14:13
@gsteel
Copy link
Member Author

gsteel commented Mar 5, 2025

Testing out a stricter set of QA tooling to see how we go.

Adding PHPStan to existing pipelines will help migration away from Psalm if that becomes necessary - and running both is not a bad idea anyhow!

@froschdesign
Copy link
Member

  • Add a Makefile for running QA and building docs locally

Copying the file to every repository does not seem very future-proof to me. 🤷🏻‍♂️

@gsteel
Copy link
Member Author

gsteel commented Mar 5, 2025

Copying the file to every repository does not seem very future-proof to me

Got any ideas for automating Makefile deployment to all the repos?

OTOH, It's plausible that Makefiles might diverge in different repos… Do you see it as a problem to use make? I personally much prefer it to composer scripts and things like building docker images etc can't really be done in composer.

@froschdesign
Copy link
Member

Do you see it as a problem to use make?

No, of course not but in copy and paste.

@Ocramius
Copy link
Member

Ocramius commented Mar 5, 2025

Make itself isn't really reuse-friendly.

We could make a reusable nix derivation containing a make entry-point perhaps? That would be supported by renovate.

@gsteel
Copy link
Member Author

gsteel commented Mar 5, 2025

We could make a reusable nix derivation containing a make entry-point perhaps? That would be supported by renovate.

OK, now you've lost me 😂

@gsteel
Copy link
Member Author

gsteel commented Mar 5, 2025

@Ocramius
Could adding flake.nix and flake.lock to the root of repos automate things like .gitattributes dot files, installing standalone tools in sub-directories etc?

@Ocramius
Copy link
Member

Ocramius commented Mar 5, 2025

Roughly, yes: I'm very new to it as well though 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Enhancement New feature or request QA Quality assurance tasks such as static analysis improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants