We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Downstream projects that want to leverage the payloads from pull, load, etc. need some way to parse the messages coming back. This currently lives in https://github.com/moby/moby/blob/master/pkg/jsonmessage/jsonmessage.go
Unfortunately, the type definitions are intertwined with TTY code for CLI handling.
These should be split out, ideally into the client library so downstream projects can easily consume the standard structure definitions.
The text was updated successfully, but these errors were encountered:
Please :) This is also needed for parsing output of client.ImagePull
Sorry, something went wrong.
Reference: docker/engine-api#89
/cc @stevvooe @cpuguy83
+1; unable to pull cleanly with dep. Going to hack around for now, but not ideal.
No branches or pull requests
Downstream projects that want to leverage the payloads from pull, load, etc. need some way to parse the messages coming back. This currently lives in https://github.com/moby/moby/blob/master/pkg/jsonmessage/jsonmessage.go
Unfortunately, the type definitions are intertwined with TTY code for CLI handling.
These should be split out, ideally into the client library so downstream projects can easily consume the standard structure definitions.
The text was updated successfully, but these errors were encountered: