Add CLI command for debugging

wearerequired / traduttore

🗼 A WordPress plugin to improve the I18N workflow for your own projects based on @GlotPress.

https://wearerequired.github.io/traduttore/

72 stars 12 forks source link

Add CLI command for debugging #67

Closed swissspidy closed 5 years ago

swissspidy commented 6 years ago

Some thoughts about possible WP-CLI commands for easier debugging:

`wp traduttore info`

This could show some status information, e.g. things like:

Plugin version
Path to git binary
Path to WP-CLI binary
Path to cache dir
Whether requirements (git, WP-CLI i18n-command, zip extension, Slack plugin, etc.) are met
…?

`wp traduttore debug <project>`

Repository information (type, vcs type, url, visibility)
Path to the cached repository
Whether the repository exists and Traduttore has access to it

swissspidy commented 6 years ago

Added a description to explain my thinking here :-)

ocean90 commented 6 years ago

More thoughts:

wp traduttore debug <project>

Timestamp/status of last import
Available language packs maybe with their last build time

swissspidy commented 6 years ago

Available language packs maybe with their last build time

So sort of like the API endpoint?

Maybe we could use a separate command for that to show a proper list with different --format options.

swissspidy commented 5 years ago

Timestamp/status of last import

I don't think we store that information yet. We store the last build date for language packs, but nothing for the import. Unless GlotPress does that ...?

swissspidy commented 5 years ago

Unless GlotPress does that ...?

Looking at \GP_Original::import_for_project that doesn't seem to be the case.