-
-
Notifications
You must be signed in to change notification settings - Fork 361
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.
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
nextercism: implement troubleshoot command #415
Comments
13 tasks
I'd be up for looking into implementing this next week? |
Sweet, that sounds great. |
robphoenix
added a commit
to robphoenix/exercism-cli
that referenced
this issue
Aug 15, 2017
robphoenix
added a commit
to robphoenix/exercism-cli
that referenced
this issue
Aug 17, 2017
robphoenix
added a commit
to robphoenix/exercism-cli
that referenced
this issue
Aug 17, 2017
robphoenix
added a commit
to robphoenix/exercism-cli
that referenced
this issue
Aug 18, 2017
Closed by #443 |
aldraco
pushed a commit
to aldraco/cli
that referenced
this issue
Nov 2, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To be merged into the nextercism branch in #410
Command name:
troubleshoot
(aliast
).File:
cmd/troubleshoot.go
.I chose the name
troubleshoot
rather thandebug
so that we can have a single-letter alias without crashing into thedownload
command.The current implementation (https://github.com/exercism/cli/blob/master/cmd/debug.go) is probably almost directly portable. The only difference would be that you can get a user configuration with
config.NewUserConfig()
instead of making one from scratch and populating it.UPDATE There is a second difference. We'll have an explicit
/ping
endpoint to call for the Exercism API.The text was updated successfully, but these errors were encountered: