Shohei Nakajima

Thanks for the reply. I understand the plan. Once I downgrade my environment to CakePHP 5.0 and ElasticSearch 7, I will proceed. When I can afford it, I will debug...

Regarding CakePHP 5.1 and ElasticSearch 8.x, I set the following in `config/app.php` and it worked. ```` 'elastic' => [ 'className' => 'Cake\ElasticSearch\Datasource\Connection', 'driver' => 'Cake\ElasticSearch\Datasource\Connection', 'host' => '127.0.0.1', 'port' =>...

Thank you for your response. I see that it can be omitted. However, I feel uncomfortable that `cake MyPlugin.my_command` can be executed, but `cake MyPlugin.my_command mysubcommand` cannot. In my project...

Hi @markstory , Will this issue not be fixed in CakePHP 5.x, or has it already been fixed? I’m not particularly troubled by it, so if it will be fixed...

`(OK)` cake my_plugin.my_command `(OK)` cake MyPlugin.my_command `(OK)` cake my_plugin.my_command mysubcommand `(NG)` cake MyPlugin.my_command mysubcommand When there is no subcommand, both snake_case (`my_plugin`) and CamelCase (`MyPlugin`) plugin names are supported. However,...

Is it because when accessing the URL, it supports snake case? `http://xxxx.com/my_plugin/my_controller/my_action` I assumed it was the same as this policy.

Yes, that sounds good to me.

In general CLI conventions, snake_case or kebab-case is commonly used, so I can understand the argument for standardizing on snake_case. However, when displaying the list of commands using `cake --help`,...