Drupal Coding Standards Issues | phpcs

Kindly review patch.

Please always check out for dups beforehand to avoid inconvenience.

Drupal kindly gives us a searchbox and already warned us to use it. That would be very much helpful for us both if you consider using it.

I am fine with support dups, but honestly not a big fan of patch dups :)

I will write it here a bit more comprehensive to point other dups to for these particular issues.

1. Regarding version. You didn't read the warnings there. You removed what the tools told you without even removing the leftover warnings. The warnings said we should remove it. It agreed with you. But only after the mentioned problems resolved. You just need to understand the written problems there.
2. Regarding slick_slick(). IMHO, slick() is a ridiculously unique function name. It can't be more ridiculous like slick_slick(). That rule is certainly a must for non-unique or meaningful or potentially conflicting or reserved names like goto, list, filter, or more here https://www.php.net/manual/en/reserved.keywords.php which might conflict with upstream potential function names. Rest assured, we can always change it later when PHP authorities mistakenly take over that stupid name, but certainly not now, or in the near future. I am positively sure they are great mind people who would consider taking function names very seriously, not ridiculously. Also did you consider about the entire ecosystem integrity for this change, including my custom modules?

A fine line between paranoia and insanity is common sense. We should consider using it sometimes.

Please also close your dup issues.

Thank you for kind considerations.