Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Found some coding standards that needed to be fixed.
Found some coding standards that needed to be fixed.
Comments
Comment #2
DeaOm CreditAttribution: DeaOm at Agiledrop - Your Trusted Drupal Teammates commentedComment #4
DeaOm CreditAttribution: DeaOm at Agiledrop - Your Trusted Drupal Teammates commentedFixed most of the CSS problems, the backgorund image one still remains, because it needs to be added as it's own class, so there is no repeating of the image, which is not allowed. But there was no twig template, so I hope everything still works after CSS changes. Needs review and work.
Comment #5
HongPong CreditAttribution: HongPong at kor group commentedMissing semicolon here on the background attribute. Also I believe this should be a background-image attribute if there is no positioning or size included.
Comment #6
Neslee Canil PintoCoding Standards added
Comment #8
Neslee Canil PintoUpdated Coding Standards
Comment #9
Neslee Canil PintoComment #11
Neslee Canil PintoUpdated Coding Standard
Comment #13
Neslee Canil PintoUpdated Coding Standard
Comment #15
Neslee Canil PintoUpdated Coding Standard
Comment #17
Neslee Canil PintoUpdated Coding Standard
Comment #19
Neslee Canil PintoUpdated Coding Standard
Comment #21
Neslee Canil PintoUpdated Coding Standard
Comment #23
Neslee Canil PintoFixed all coding standard issues. Build Showing Test Failed
Comment #24
HongPong CreditAttribution: HongPong at kor group commentedThis cleanup looks good to me. @Neslee Canil Pinto keep in mind that "failed testing" results right now are to be expected since the test framework code has not been revised much if at all yet. The only problem you should be concerned about is if the patch doesn't apply, I believe. (also in most cases the test frameworks here are not aware of CSS in general)
Comment #25
Neslee Canil PintoOk @HongPong
So Further how should I proceed
Comment #26
HongPong CreditAttribution: HongPong at kor group commentedThese all appear to be the correct changes to me in this case. I have not tested this patch but it covers: replacing ID with class; capitalization; removing !important tags (yes!). This brings us much closer to correct CSS. So with the point we are at now, I think it should be committed, but we should get another opinion for more certainty.
Also in the future we need to be aware, as you covered in this patch, that there are multiple CSS files to keep track of on this module (we have seen other patches that did not cover some of them).
I think we could approve this and move onto #2490318: Administration Menu Javascript ESLint errors to cover the Javascript equivalent/similar code style issues. All of this helps because then we won't get tons of confusing code smell warnings, moving into the trickier issues later. Thanks again!!
Comment #27
Neslee Canil PintoHey HongKong
Can you commit this patch
https://www.drupal.org/project/admin_menu/issues/3005007#comment-12937138
Comment #28
HongPong CreditAttribution: HongPong at kor group commented@Neslee if I can get a little time I will test it today and if it's solid I will commit it.
Comment #29
Neslee Canil PintoOk @HongPong take your time👍
Comment #30
thallesReplacing # admin-menu by .admin-menu would not break any menu?
Comment #31
pifagorIn my opinion, this should not be done.
Comment #32
thallesThis module has been deprecated for Drupal 8.
For Drupal 8: the Admin Toolbar provides an experience similar to admin_menu with the core toolbar.
Thanks @all!