Check PHPStan in addons #1592

Merged
MrPetovan merged 2 commits from Art4/friendica-addons:fix-phpstan-error into develop 2025-01-23 14:30:00 +01:00
Contributor

I noticed that #1589 adds a PHPStan warning that was not noticed in the review. This leads now to failing tests in the friendica repository.

This PR fixes the error and tries to introduce PHPStan tests in the addon repository to avoid this situation in the future.

Update 1: In the meanwhile #1590 was merged. I resolved the merge conflict.

Update 2: And now I noticed #1591 😆

I noticed that #1589 adds a PHPStan warning that was not noticed in the review. This leads now to failing tests in the friendica repository. This PR fixes the error and tries to introduce PHPStan tests in the addon repository to avoid this situation in the future. **Update 1**: In the meanwhile #1590 was merged. I resolved the merge conflict. **Update 2**: And now I noticed #1591 😆
Art4 added 1 commit 2025-01-22 09:46:21 +01:00
Art4 added 1 commit 2025-01-22 09:47:03 +01:00
Art4 added 1 commit 2025-01-22 09:50:34 +01:00
Owner

Concerning the warning: Couldn't the addons be excluded from that? Because currently this leads to a situation where you have to fix something in the addons to make the core work - and this doesn't sound right.

Concerning the warning: Couldn't the addons be excluded from that? Because currently this leads to a situation where you have to fix something in the addons to make the core work - and this doesn't sound right.
Owner

I'm currently getting a merge conflict when I try to accept rhe PR.

I'm currently getting a merge conflict when I try to accept rhe PR.
Author
Contributor

Concerning the warning: Couldn't the addons be excluded from that? Because currently this leads to a situation where you have to fix something in the addons to make the core work - and this doesn't sound right.

This warning occurs because we don't have checks on the addon repository. If we had this check established, we wouldn't run into this situation.

The addon repository depends on the friendica repository. That's why we a.) run checks in friendica repository so a breaking change there should notified early and b.) should run checks on the addon repository to avoid situations like #1589.

As long as we don't have a documented contract or other mechanisms between these repos I recommend that we keep this checks.

> Concerning the warning: Couldn't the addons be excluded from that? Because currently this leads to a situation where you have to fix something in the addons to make the core work - and this doesn't sound right. This warning occurs because we don't have checks on the addon repository. If we had this check established, we wouldn't run into this situation. The addon repository depends on the friendica repository. That's why we a.) run checks in friendica repository so a breaking change there should notified early and b.) should run checks on the addon repository to avoid situations like #1589. As long as we don't have a documented contract or other mechanisms between these repos I recommend that we keep this checks.
Author
Contributor

I cannot see if woodpecker jobs are running on this repository. Are the actions configured correctly and activated?

I cannot see if woodpecker jobs are running on this repository. Are the actions configured correctly and activated?
MrPetovan force-pushed fix-phpstan-error from 27c3572a96 to 7a7940a8ed 2025-01-23 14:29:23 +01:00 Compare
MrPetovan added the
2025.02
label 2025-01-23 14:29:29 +01:00
MrPetovan approved these changes 2025-01-23 14:29:46 +01:00
MrPetovan merged commit 69e75ef88b into develop 2025-01-23 14:30:00 +01:00
Author
Contributor

@MrPetovan I'm a bit confused. Are actions and runners are activated in this repo?

@MrPetovan I'm a bit confused. Are actions and runners are activated in this repo?
Art4 deleted branch fix-phpstan-error 2025-01-24 00:34:18 +01:00
Owner

It doesn't look like it but I don't pay attention to it. Maybe @nupplaPhil would be able to answer this question better.

It doesn't look like it but I don't pay attention to it. Maybe @nupplaPhil would be able to answer this question better.
Owner

IIRC the CI only allowes one target - github or self-hosted service - and as long as the bug that prevents us from importing the core repos history and issues is not solved upstream, we are bound to check either core or addons.

IIRC the CI only allowes one target - github or self-hosted service - and as long as the bug that prevents us from importing the core repos history and issues is not solved upstream, we are bound to check either core or addons.
Author
Contributor

IIRC the CI only allowes one target - github or self-hosted service - and as long as the bug that prevents us from importing the core repos history and issues is not solved upstream, we are bound to check either core or addons.

Ok, thank you for this information. This seems to be a problem. And as long as we couldn't run the CI on the addons only we should definitely keep the tests running for the addons in the friendica repository.

> IIRC the CI only allowes one target - github or self-hosted service - and as long as the bug that prevents us from importing the core repos history and issues is not solved upstream, we are bound to check either core or addons. Ok, thank you for this information. This seems to be a problem. And as long as we couldn't run the CI on the addons only we should definitely keep the tests running for the addons in the friendica repository.
Sign in to join this conversation.
No description provided.