Kevin Pfeifer

just so i can give my 2 last cents about this: i dont mind either way. Just wanted to make stuff a bit more consistent. If this is too much...

https://github.com/cakephp/upgrade/blob/5.x/config/rector/sets/cakephp50.php#L107C6-L107C18 its basically this which gets filled with data from a massive array

TLDR: Too many BC changes just for consistent code style. Lets just keep it the way it is... as always

I'd say we can close this since all methods have now been renamed in `6.x` 🥳

Just to be clear: You are actually talking about paginating those results in a web request to show them in a e.g. table. Otherwise I thought [chunking](https://book.cakephp.org/5/en/core-libraries/collections.html#Cake\Collection\Collection::chunk) is all one...

Why do we support snake case plugin names here? Pretty much everywhere else we use/prefer/documented the camel case version. Is this something that is specific to commands?

The pattern in the URL is defined by the [RouteClass which by default is the dashed route](https://github.com/cakephp/app/blob/5.x/config/routes.php#L50), so your case would be ``` http://xxxx.com/my-plugin/my-controller/my-action ``` But nonetheless, URL patterns shouldn't...

> The UI world's current darling, Tailwind CSS, also doesn't seem to expect checkboxes/radios nested inside labels. Depends on what tailwind based package you use. [Flowbite](https://flowbite.com/docs/forms/checkbox/) doesn't nest but [DaisyUI](https://daisyui.com/components/checkbox/)...

FYI: Tailwind UI is one of many Tailwind based component libraries 😉 Tailwind itself is just the tool, that maps 1 HTML class to 1 CSS prop/feature/behavior

Can this be closed since a solution has been found?