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

Switch phpstan to include phpstan.neon.dist #249

Closed
deviantintegral opened this issue Aug 22, 2023 · 3 comments · Fixed by #627
Closed

Switch phpstan to include phpstan.neon.dist #249

deviantintegral opened this issue Aug 22, 2023 · 3 comments · Fixed by #627
Assignees
Labels
bug Something isn't working client affected

Comments

@deviantintegral
Copy link
Member

As I noted at #216, phpstan generally recommends and expects a .dist file to be committed to the repo, and phpstan.neon to be git ignored. As well, PHPStorm throws an error that phpstan.neon.dist doesn't exist.

Instead, lets:

  1. Copy the configuration as phpstan.neon.dist via composer scaffold.
  2. Get rid of -c in our task:static tests.
@davereid
Copy link
Member

davereid commented Jan 8, 2024

Yes, +1 to this, using a phpstan.neon.dist is preferred and what we provided via scaffolding on a shared install profile across several sites, which allows individual projects to still use their own phpstan.neon file that overrides/references the dist file already.

@deviantintegral deviantintegral added bug Something isn't working client affected labels Feb 19, 2024
@deviantintegral
Copy link
Member Author

Same type of issue as #238 .

@leonel-lullabot
Copy link
Collaborator

PR #627 is ready for review

mrdavidburns pushed a commit that referenced this issue Aug 5, 2024
* Issue #249: Remove -c from the phpstan test

* Issue #249: Scaffold phpstan.neon.dist

* Issue #249: Update TestStatic.yml

* Issue #249: Update phpstan.neon.dist
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working client affected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants