Skip to content

Conversation

@kesselb
Copy link
Collaborator

@kesselb kesselb commented Jul 10, 2020

Signed-off-by: Daniel Kesselberg mail@danielkesselberg.de

@kesselb kesselb force-pushed the enh/hello-psalm branch 7 times, most recently from 6696326 to 3f2d081 Compare July 15, 2020 20:22
@kesselb kesselb force-pushed the enh/hello-psalm branch 2 times, most recently from 449ef09 to e39e4c9 Compare August 10, 2020 20:02
@MorrisJobke
Copy link
Member

How nice is this? 😍 👍

@MorrisJobke MorrisJobke self-requested a review August 14, 2020 09:26
@kesselb
Copy link
Collaborator Author

kesselb commented Aug 14, 2020

Yep. PHPStorm is going to add support for Psalm soon: https://blog.jetbrains.com/phpstorm/2020/07/phpstan-and-psalm-support-coming-to-phpstorm/.

I'm not sure yet how to continue with this PR. I fixed some errors or added rules to suppress them (like the global template variables $_ and $l). But there are still more than 1000 warnings.

There are some false positives left. But others warning are legit. To continue and merge this PR we could set a baseline (https://psalm.dev/docs/running_psalm/dealing_with_code_issues/#using-a-baseline-file) with the current errors. With the risk that no one will fix the existing issues ;)

@MorrisJobke
Copy link
Member

There are some false positives left. But others warning are legit. To continue and merge this PR we could set a baseline (https://psalm.dev/docs/running_psalm/dealing_with_code_issues/#using-a-baseline-file) with the current errors. With the risk that no one will fix the existing issues ;)

I guess that is the only way to go for now.

MorrisJobke added a commit that referenced this pull request Aug 17, 2020
Ref #21787

Signed-off-by: Morris Jobke <hey@morrisjobke.de>
MorrisJobke added a commit that referenced this pull request Aug 17, 2020
Ref #21787

Signed-off-by: Morris Jobke <hey@morrisjobke.de>
MorrisJobke added a commit that referenced this pull request Aug 17, 2020
Ref #21787

Signed-off-by: Morris Jobke <hey@morrisjobke.de>
@MorrisJobke
Copy link
Member

There are some false positives left. But others warning are legit. To continue and merge this PR we could set a baseline (https://psalm.dev/docs/running_psalm/dealing_with_code_issues/#using-a-baseline-file) with the current errors. With the risk that no one will fix the existing issues ;)

I guess that is the only way to go for now.

Mind to do this now and then we could merge this :)

@skjnldsv
Copy link
Member

I thought it was a dashboard widget to display Psalm quotes 😁

Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
for some reason they are not loaded by default.

Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
@MorrisJobke
Copy link
Member

MorrisJobke commented Aug 18, 2020

@MorrisJobke MorrisJobke force-pushed the enh/hello-psalm branch 3 times, most recently from 940db3d to 977aace Compare August 18, 2020 10:46
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
…heck

Signed-off-by: Morris Jobke <hey@morrisjobke.de>
@nextcloud nextcloud deleted a comment from faily-bot bot Aug 18, 2020
@MorrisJobke
Copy link
Member

Here it is - the final rebase that squashed all the fixups into the proper commits. It now also warns about not checked in fixes (so if we fix something it also states that the baseline should be updated).

@MorrisJobke MorrisJobke added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Aug 18, 2020
@MorrisJobke MorrisJobke merged commit 92b6740 into master Aug 18, 2020
@MorrisJobke MorrisJobke deleted the enh/hello-psalm branch August 18, 2020 11:38
'ocs',
'package-lock.json',
'package.json',
'psalm.xml',
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We don't need psalm baseline here?

Copy link
Member

Choose a reason for hiding this comment

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

No - because it's in the build/ folder which is deleted already. Only new files in the root need to be checked if the release script should either delete them or keep them. I went for the "delete the psalm.xml in the release" way. :)

kesselb pushed a commit that referenced this pull request Aug 31, 2020
Ref #21787

Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish enhancement technical debt

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants