Skip to content

rector#1062

Merged
LordSimal merged 1 commit into5.nextfrom
5.next-rector
Mar 29, 2026
Merged

rector#1062
LordSimal merged 1 commit into5.nextfrom
5.next-rector

Conversation

@LordSimal
Copy link
Copy Markdown
Contributor

This would be changed by rector if we added it to debug_kit. Would love to see this across all our plugins to get more consistency.

Woud be cool if we could somehow unify the rector config across repositories though.

The shared CI workflow also needs to be adjusted to execute rector (if its present)

@LordSimal
Copy link
Copy Markdown
Contributor Author

Refs: cakephp/.github#26

Copy link
Copy Markdown
Member

@markstory markstory left a comment

Choose a reason for hiding this comment

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

The changes rector applied seem good to me. Would we be able to put rector.php into a package that we can share across plugins?

@LordSimal
Copy link
Copy Markdown
Contributor Author

A shared (or at least baseline) rector config would be great, but we'd need to add it to something all projects depend on.

The rector config is just a object with chainable config calls, so it would be just 1 additional require before the rector.php in each package using it.

We could of course also just make an additional package/repo and add it as a dev dependency, but I don't know if this is the best way to go.

@LordSimal LordSimal marked this pull request as ready for review March 29, 2026 09:37
@LordSimal LordSimal merged commit b415a72 into 5.next Mar 29, 2026
14 of 16 checks passed
@LordSimal LordSimal deleted the 5.next-rector branch March 29, 2026 09:37
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