Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add CLI command for debugging #67

Closed
swissspidy opened this issue Oct 24, 2018 · 5 comments
Closed

Add CLI command for debugging #67

swissspidy opened this issue Oct 24, 2018 · 5 comments
Labels
[Component] CLI CLI commands and tooling
Milestone
3.0.0

Comments

@swissspidy
Copy link
Collaborator

swissspidy commented Oct 24, 2018 •
edited
Loading

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 swissspidy mentioned this issue Oct 24, 2018
Open
@swissspidy swissspidy added this to the 3.1.0 milestone Oct 26, 2018
@swissspidy
Copy link
Collaborator Author

Added a description to explain my thinking here :-)

@swissspidy swissspidy added the [Component] CLI CLI commands and tooling label Oct 30, 2018
swissspidy added a commit that referenced this issue Nov 5, 2018
@swissspidy
First pass at InfoCommand
2b85c98 
See #67.
@swissspidy swissspidy mentioned this issue Nov 5, 2018
Merged
3 tasks
@ocean90
Copy link
Member

ocean90 commented Nov 9, 2018

More thoughts:

wp traduttore debug <project>

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

@swissspidy
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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 added a commit that referenced this issue Nov 11, 2018
@swissspidy
First pass at project command for debugging
f6aa0d6 
See #67.
@swissspidy swissspidy mentioned this issue Nov 11, 2018
Merged
3 tasks
swissspidy added a commit that referenced this issue Nov 13, 2018
@swissspidy
Project CLI command (#110)
d47a01e 
Adds two new WP-CLI commands:

* `wp traduttore project info <project>` (similar to `wp traduttore info`)
* `wp traduttore project list <project>`

Also adds the `wp traduttore build` and `wp traduttore update` commands to the `project` namespace for increased consistency. So the commands now work like this:

* `wp traduttore project build <project>`
* `wp traduttore project update <project>`

Fixes #67.
@swissspidy
Copy link
Collaborator Author

Unless GlotPress does that ...?

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

@swissspidy swissspidy mentioned this issue Nov 13, 2018
Closed
@grappler grappler modified the milestones: 3.1.0, 3.0.0 Mar 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Component] CLI CLI commands and tooling
Projects
None yet
Milestone
3.0.0
Development

No branches or pull requests
3 participants
@ocean90 @swissspidy @grappler