Swagger not displaying all response fields in Apiary
I have the following swagger definition:
ShippingMethod:
required:
- id
- code
- description
- type
type: object
properties:
id:
title: Id
type: string
maxLength: 36
minLength: 1
distributor:
title: Distributor
type: string
maxLength: 255
minLength: 1
code:
title: Code
type: string
maxLength: 255
minLength: 1
description:
title: Description
type: string
minLength: 1
type:
title: Type
type: string
maxLength: 255
minLength: 1
In the editor at swagger.io it shows me the response I require for a GET call (list):
[
{
"id": "string",
"distributor": "string",
"code": "string",
"description": "string",
"type": "string"
}
]
But when using the same in Apiary it translates to the following response:
[
{
"id": "exercitation quis",
"code": "est",
"description": "laborum veniam",
"type": "cupidatat proident sed"
},
{
"id": "officia sint consequat Ut",
"code": "sit mollit",
"description": "consectetur qui aute esse ut",
"type": "nisi Excepteur velit dolor"
}
]
Distributor will be a field in the response, yet it is not shown in the Apiary rendered response. It will shop up when making it required in the definition, but that is not what I want.
How can I ensure that these optional fields do appear in the response?
swagger apiary.io
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
add a comment |
I have the following swagger definition:
ShippingMethod:
required:
- id
- code
- description
- type
type: object
properties:
id:
title: Id
type: string
maxLength: 36
minLength: 1
distributor:
title: Distributor
type: string
maxLength: 255
minLength: 1
code:
title: Code
type: string
maxLength: 255
minLength: 1
description:
title: Description
type: string
minLength: 1
type:
title: Type
type: string
maxLength: 255
minLength: 1
In the editor at swagger.io it shows me the response I require for a GET call (list):
[
{
"id": "string",
"distributor": "string",
"code": "string",
"description": "string",
"type": "string"
}
]
But when using the same in Apiary it translates to the following response:
[
{
"id": "exercitation quis",
"code": "est",
"description": "laborum veniam",
"type": "cupidatat proident sed"
},
{
"id": "officia sint consequat Ut",
"code": "sit mollit",
"description": "consectetur qui aute esse ut",
"type": "nisi Excepteur velit dolor"
}
]
Distributor will be a field in the response, yet it is not shown in the Apiary rendered response. It will shop up when making it required in the definition, but that is not what I want.
How can I ensure that these optional fields do appear in the response?
swagger apiary.io
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
add a comment |
I have the following swagger definition:
ShippingMethod:
required:
- id
- code
- description
- type
type: object
properties:
id:
title: Id
type: string
maxLength: 36
minLength: 1
distributor:
title: Distributor
type: string
maxLength: 255
minLength: 1
code:
title: Code
type: string
maxLength: 255
minLength: 1
description:
title: Description
type: string
minLength: 1
type:
title: Type
type: string
maxLength: 255
minLength: 1
In the editor at swagger.io it shows me the response I require for a GET call (list):
[
{
"id": "string",
"distributor": "string",
"code": "string",
"description": "string",
"type": "string"
}
]
But when using the same in Apiary it translates to the following response:
[
{
"id": "exercitation quis",
"code": "est",
"description": "laborum veniam",
"type": "cupidatat proident sed"
},
{
"id": "officia sint consequat Ut",
"code": "sit mollit",
"description": "consectetur qui aute esse ut",
"type": "nisi Excepteur velit dolor"
}
]
Distributor will be a field in the response, yet it is not shown in the Apiary rendered response. It will shop up when making it required in the definition, but that is not what I want.
How can I ensure that these optional fields do appear in the response?
swagger apiary.io
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
I have the following swagger definition:
ShippingMethod:
required:
- id
- code
- description
- type
type: object
properties:
id:
title: Id
type: string
maxLength: 36
minLength: 1
distributor:
title: Distributor
type: string
maxLength: 255
minLength: 1
code:
title: Code
type: string
maxLength: 255
minLength: 1
description:
title: Description
type: string
minLength: 1
type:
title: Type
type: string
maxLength: 255
minLength: 1
In the editor at swagger.io it shows me the response I require for a GET call (list):
[
{
"id": "string",
"distributor": "string",
"code": "string",
"description": "string",
"type": "string"
}
]
But when using the same in Apiary it translates to the following response:
[
{
"id": "exercitation quis",
"code": "est",
"description": "laborum veniam",
"type": "cupidatat proident sed"
},
{
"id": "officia sint consequat Ut",
"code": "sit mollit",
"description": "consectetur qui aute esse ut",
"type": "nisi Excepteur velit dolor"
}
]
Distributor will be a field in the response, yet it is not shown in the Apiary rendered response. It will shop up when making it required in the definition, but that is not what I want.
How can I ensure that these optional fields do appear in the response?
swagger apiary.io
swagger apiary.io
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
asked Nov 23 '18 at 9:12
God SerenaGod Serena
288
288
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443621%2fswagger-not-displaying-all-response-fields-in-apiary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443621%2fswagger-not-displaying-all-response-fields-in-apiary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
