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

Make QA tools available by default #81

Merged
merged 5 commits into from
Jan 8, 2024
Merged

Conversation

Xerkus
Copy link
Member

@Xerkus Xerkus commented Nov 28, 2023

Q A
Documentation no
Bugfix no
BC Break no
New Feature yes
RFC no
QA yes

Description

Default installation results in tests, static analysis and coding standard tools are unusable. By making sure QA tools are immediately available and passing with composer test, composer cs-check and composer static-analysis we can promote their adoption and provide better starting point for our users.

I included phpstorm and psalm stubs for container that I often find in my own projects. While it is not a strict relation between class-string id and actual returned instance it tends to be true often enough.

Signed-off-by: Aleksei Khudiakov <aleksey@xerkus.pro>
@Xerkus Xerkus added this to the 2.3.0 milestone Nov 28, 2023
Signed-off-by: Aleksei Khudiakov <aleksey@xerkus.pro>
Signed-off-by: Aleksei Khudiakov <aleksey@xerkus.pro>
Signed-off-by: Aleksei Khudiakov <aleksey@xerkus.pro>
Copy link
Member

@gsteel gsteel left a comment

Choose a reason for hiding this comment

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

I think this is really good improvement. Just a couple of minor comments from me 👍

psalm.xml Outdated Show resolved Hide resolved
displayDetailsOnTestsThatTriggerErrors="true"
displayDetailsOnTestsThatTriggerNotices="true"
displayDetailsOnTestsThatTriggerWarnings="true"
colors="true"
Copy link
Member

Choose a reason for hiding this comment

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

Do you think that failOnWarning, failOnNotice and friends would be too strict?

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think this controls whether phpunit fails on warnings. This makes phpunit report tests that produced warnings or notices in test results.

Copy link
Member

Choose a reason for hiding this comment

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

Sorry - I meant: Do you think that failOnWarning and friends should be added to PHPUnit's config?

Copy link
Member Author

Choose a reason for hiding this comment

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

They should.
Not the decision I am going to make here. We don't use them. Users can tighten configuration themselves.

Signed-off-by: Aleksei Khudiakov <aleksey@xerkus.pro>
@Xerkus Xerkus merged commit 27be3a7 into laminas:2.3.x Jan 8, 2024
10 checks passed
@Xerkus Xerkus deleted the feature/qa-tools branch January 8, 2024 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants