[ibexa/rector] Backported Ibexa Rector recipe to 4.6 #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR backports
5.0
configuration to4.6
.4.6
branch is already available foribexa/rector
package.Ibexa 5.0 set contains deprecations that should be removed in 4.6 anyway.
There might be some minor differences (like we deprecated something in 5.0 only). We could approach that in several ways:
5.0
set list between4.6
and5.0
branches inibexa/rector
package,5.0
set as the4.6
set with changes,5.0
rules are executable on4.6
.WDYT?
Edit: after today's dry run for the presentation the conclusion was that having
IBEXA_46
set would look less confusing in case of 4.6.Note: ideally we take conclusions as follow up changes, because I need this recipe for Ibexa Summit this week.