Skip to content

Conversation

@EmanFateen
Copy link
Contributor

@EmanFateen EmanFateen commented Dec 10, 2025

Q A
Tickets Fix #
License MIT

Description:

While working on upgrading PHP to v8.4, I found that PSLAM v5 is a blocker, and it needs to be upgraded to v6.
I've opened this PR to upgrade PSLAM to v6.

Key changes:

  • Upgrade PSLAM version to v6
  • set pslam-baseline xml file.

@EmanFateen EmanFateen requested a review from imdhemy as a code owner December 10, 2025 21:40
@EmanFateen EmanFateen marked this pull request as draft December 10, 2025 21:40
@EmanFateen EmanFateen marked this pull request as ready for review December 11, 2025 16:47
@EmanFateen EmanFateen mentioned this pull request Dec 11, 2025
5 tasks
@imdhemy
Copy link
Owner

imdhemy commented Dec 11, 2025

@EmanFateen
Linking the PR to the issue will close it once this PR is merged. Either remove the issue from the description table or file a new issue for this PR.

@EmanFateen
Copy link
Contributor Author

@imdhemy I removed the issue from the description table.

@imdhemy
Copy link
Owner

imdhemy commented Dec 11, 2025

@EmanFateen
It's a good idea to separate Psalm into a different PR. I checked the Psalm errors and they fall into two groups:

1. Unused code

Psalm 6 changed the default configuration to detect unused code.

[BC] Property Config::$find_unused_code changed default value from false to true.

We can mark some parts as public API, as mentioned in the Psalm docs
(class, method).

But we still need to handle PossiblyUnusedProperty, because it seems to be a real issue.

2. Laravel code

This includes the config() helper and the console commands. We are already using the Psalm Laravel Plugin, but it is not upgraded yet.

https://github.com/EmanFateen/laravel-in-app-purchases/blob/fea74577326eef7c760c5b56eb16996f6854696c/composer.json#L30

The plugin can't be upgraded because it conflicts with the version required by orchestra/testbench, and we need to update that first.

I think we should upgrade orchestra/testbench and bump the minimum laravel/framework version, so we can still get the full advantage of Psalm.

What do you think?

Copy link
Owner

@imdhemy imdhemy left a comment

Choose a reason for hiding this comment

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

  • Upgrade orchestra/testbench.
  • Upgrade psalm/plugin-laravel.
  • Address Psalm issues.

@imdhemy
Copy link
Owner

imdhemy commented Dec 12, 2025

I think we should upgrade orchestra/testbench and bump the minimum laravel/framework version, so we can still get the full advantage of Psalm.

@EmanFateen I addressed this in this PR #490

Let's upgrade the Psalm laravel plugin as well, and check how many issues we get.

@EmanFateen
Copy link
Contributor Author

@imdhemy Thank you! I'm on it.
I'll Upgrade psalm/plugin-laravel. then revisit your comment about the Psalm issues.

Copy link
Owner

@imdhemy imdhemy left a comment

Choose a reason for hiding this comment

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

@EmanFateen Thanks a million!

@imdhemy imdhemy merged commit 7be1f4d into imdhemy:1.x Dec 13, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants