I modified the prompt (English only for now) so that it generates the reply in the same language as the original email. Previously, the answers were always generated in English even though I receive emails in multiple languages.

(Good job for this extension by the way and thank you for open sourcing it.)

Improved prompt to reply in the same language

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

Removed psr autoloader because "src" folder doesn't exist

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

Actually, there is nothing to autoload here. Closing this.

Also, if you're willing to, could you also include wp-cli/.github#41 (either as a separate PR or in the PR)?

I think it might be best to do the code beautifier change in another PR. Unfortunately, I don't think I'll be able to do this though (at least not anytime soon). It potentially changes a lot of code requiring testing and it could lead to a bit of follow up work which I might not be able to do over the next weeks and months because my personal priorities will change soon: 👶

The PRs for entity-command and shell-command are slightly different compared to the PRs on the other commands, because part of the code is namespaced while another part is not. I still propose to replace the psr-4 autoloader with a classmap for now, until everything is namespaced.

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This PR is slightly different compared to the PRs on the other commands, because part of the code is namespaced while another part is not. I still propose to replace the psr-4 autoloader with a classmap for now, until everything is namespaced.

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This PR is slightly different compared to the PRs on the other commands, because part of the code is namespaced while another part is not. I still propose to replace the psr-4 autoloader with a classmap for now, until everything is namespaced.

Replace empty namespace autoloader with classmap

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

Replace empty namespace autoloader with classmap

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

Sorry for spamming you with PRs ;-) I changed the autoloader almost everywhere now.

The following packages are already properly namespaced, so no changes required here:

• i18n-command
• scaffold-package-command
• maintenance-mode-command
• profile-command
• embed-command

The doctor-command includes its own autoloader, but that is also namespaced, so not part of the scope of this performance fix, but at some point it could be refactored to use the composer autoloader.

I'll look into entity-command and shell-command now. Those two use a mix of namespaced and non-namespaced autoloaders.

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731

This fixes the issue described here: https://github.com/wp-cli/wp-cli/issues/5731