Skip to content

Conversation

@provokateurin
Copy link
Member

Summary

Based on #52853.

The idea is to prevent any new code to use already deprecated stuff. It will not be possible everywhere since we sometimes have no replacement, but then it should just be added to the baseline.
This change adds a lot to the baseline, but it's basically just a todo list for technical debt cleanups :)

Checklist

@provokateurin provokateurin added this to the Nextcloud 32 milestone May 15, 2025
@provokateurin provokateurin requested a review from a team as a code owner May 15, 2025 09:56
@provokateurin provokateurin requested review from nfebe and skjnldsv and removed request for a team May 15, 2025 09:56
Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

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

PR authors will hate Psalm and not the reviewer who points these out. I'm in 👍

nit: semantic commit is ci or chore but not feat as there is no new feature added to the product 🤓

Base automatically changed from refactor/rector-top-level to master May 15, 2025 10:41
@provokateurin provokateurin merged commit 2a01454 into master May 15, 2025
119 checks passed
@provokateurin provokateurin deleted the feat/psalm/error-deprecations branch May 15, 2025 10:46
mejo- added a commit to nextcloud/text that referenced this pull request May 20, 2025
mejo- added a commit to nextcloud/collectives that referenced this pull request May 20, 2025
@skjnldsv skjnldsv mentioned this pull request Aug 19, 2025
@skjnldsv skjnldsv modified the milestones: Nextcloud 32, Nextcloud 33 Sep 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants