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.

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

Remove one JSON related MUST requirement #446

Merged
merged 1 commit into from
May 26, 2016

Conversation

hqhq
Copy link
Contributor

@hqhq hqhq commented May 23, 2016

JSON is not a mandatory format, we should not use MUST
requirement on this.

Signed-off-by: Qiang Huang h.huangqiang@huawei.com

JSON is not a mandatory format, we should not use MUST
requirement on this.

Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
@wking
Copy link
Contributor

wking commented May 23, 2016

On Mon, May 23, 2016 at 02:09:14AM -0700, Qiang Huang wrote:

JSON is not a mandated format, we should not use MUST requirement on
this.

For some background on this, see 1. My main concern is “how will
callers handle this if they don't know what format the response is
in?” But looking back on it now, that's a more general “What API does
the runtime expose to its callers?” question, so I'm fine punting this
requirement to 2 or similar.

@crosbymichael
Copy link
Member

LGTM

It makes sense in the context of the actions that are being discussed in that section.

@crosbymichael crosbymichael added this to the 1.0.0 milestone May 25, 2016
@mrunalp
Copy link
Contributor

mrunalp commented May 26, 2016

LGTM

@mrunalp mrunalp merged commit 32601fb into opencontainers:master May 26, 2016
@hqhq hqhq deleted the hq_remove_MUST_JSON branch May 27, 2016 01:02
@wking wking mentioned this pull request May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants