Skip to content

Backported Rector Set for Ibexa 4.6 #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 17 commits into from
Mar 13, 2025
Merged

Backported Rector Set for Ibexa 4.6 #30

merged 17 commits into from
Mar 13, 2025

Conversation

alongosz
Copy link
Member

@alongosz alongosz commented Mar 12, 2025

🎫 Issue n/a

Related PRs:

Description:

To enable Partner Developers to adopt Ibexa Rector earlier and address deprecations already present in Ibexa 4.6, we've decided to introduce a Rector set specifically for version 4.6. Initially, it will be mostly a copy of the 5.0 set, but over time, the two will diverge.

The downside is of course code duplication. Do we have other ideas how to avoid it?

Backports from 5.0.x-dev (main) into 4.6 set:

@alongosz alongosz changed the title Prepared Rector Set for Ibexa 4.6 Backported Rector Set for Ibexa 4.6 Mar 12, 2025
@alongosz alongosz marked this pull request as ready for review March 12, 2025 14:52
@alongosz alongosz requested a review from a team March 13, 2025 09:18
@alongosz alongosz force-pushed the backport-5.0-to-4.6-set branch from 54e5a60 to 11421d3 Compare March 13, 2025 10:51
@konradoboza konradoboza requested a review from a team March 13, 2025 11:09
@konradoboza konradoboza requested a review from a team March 13, 2025 13:11
@barw4 barw4 requested a review from a team March 13, 2025 13:12
@alongosz
Copy link
Member Author

Tested with Ibexa Commerce 4.6.x-dev.

@alongosz alongosz merged commit 42bab2c into 4.6 Mar 13, 2025
3 checks passed
@alongosz alongosz deleted the backport-5.0-to-4.6-set branch March 13, 2025 23:29
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.

3 participants