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

Move phpstan configs to skeleton #664

Merged
merged 1 commit into from
Feb 16, 2022

Conversation

hgajjar
Copy link

@hgajjar hgajjar commented Feb 11, 2022

Projects would need to overwrite this files very often, so it belongs to skeleton rather than overlay

Projects would need to overwrite this files very often, so it belongs to skeleton rather than overlay
@kierenevans
Copy link
Contributor

kierenevans commented Feb 11, 2022

I agree with the phpstan-baseline.neon move, but not sure about the phpstan.neon move - all projects should have the same set of standards

@Chemaclass
Copy link
Contributor

I agree with the phpstan-baseline.neon move, but not sure about the phpstan.neon move - all projects should have the same set of standards

I am not sure about that, @kierenevans. There might be projects where the level might be different, but especially the ignoreErrors could be totally different depending on the project, no? For example, I am working on a project where I definitely have errors that I want to ignore on purpose that are 100% for our project level.

@hgajjar
Copy link
Author

hgajjar commented Feb 15, 2022

@kierenevans thanks for your review, but I also agree with @Chemaclass. Also, we keep it under skeleton in magento2 harness too - https://github.com/inviqa/harness-base-php/blob/1.3.x/src/magento2/application/skeleton/phpstan.neon
Would you agree with it?

@kierenevans
Copy link
Contributor

True, okay 👍

@hgajjar hgajjar merged commit ee7161e into 1.3.x Feb 16, 2022
@hgajjar hgajjar deleted the misc-move-phpstan-config-to-skeleton branch February 16, 2022 04:55
@andytson-inviqa andytson-inviqa added enhancement New feature or request harness-all Changes required to all harness directories labels Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request harness-all Changes required to all harness directories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants