-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
empty labels for checkbox items are removed #4238
Comments
The website getrector.com doesn't include TYPO3 stuff, so this can't work. This used to work in the past though but the template is outedated. sorry. Changelogs:
Can you please have a a look at both? I guess this one causes the problem: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72056 |
Yes I agree, I just don't know how to make TYPO3 and rector happy with the same notation. The contradiction seems being inside TYPO3 itself already, I think. |
The best is to have a look at the styleguide extension. Having a look at https://review.typo3.org/c/Packages/TYPO3.CMS/+/72056/2/typo3/sysext/backend/Tests/Unit/Utility/BackendUtilityTest.php#b505 it might be that my migration is wrong. Let me add a test case... |
your example looks outdated as it never has the |
No, in this case both rules depend on each other. This should just remove index 1 and the other one linked above should then change index 0 to "label". |
ok, I can't follow completely, as my example looks differently, but let's see what you're coming forward with |
Bug Report
In definitions like this:
the item-array gets completely removed by the typo3-rector rules
SimplifyCheckboxItemsTCARector
andMigrateItemsIndexedKeysToAssociativeRector
, both have to be excluded to keep the definitions.Minimal PHP Code Causing Issue
Sorry, I don't know how to load the Ssch namespace there:
https://getrector.com/demo/890354e6-9ea1-439a-95d7-fe7bf1e798eb
Expected Behaviour
the "items" array is required by TYPO3 and shouldn't be removed entirely.
One item with label is also required, even if it's empty.
The text was updated successfully, but these errors were encountered: