How to Report Errors in Discovery V3 Specification - required parameters missing on drive.about.get
up vote
1
down vote
favorite
drive.about.get is described by
the revision 20181101 discovery document in which the endpoint for drive:v3.about.get does not include the standard parameters included in the API EXplorer.
V3 is listed as the preferred version.
Given that the fields parameter is required and expects a keyed value from The returned 'about' resource description I expect that this is an erroneous omission from the discovery specification.
Although it is simple enough to work around this, for me it requires additional documentation to explain the requirement.
I note that this is the first Drive endpoint I have explored - I expect that as I continue I will see more missing required parameter specifications. Perhaps this part of the Google Discovery API schema is optional?
My question is - what is the process to help correct this? How frequently are the discovery specs updated and is it up the the user to monitor these changes.
As an additional note for users - you can provide a fields query parameter value of '*' to return all fields. This has also been touched on in Revisions list and get missing information
Any guidance welcome.
google-drive-sdk asked Nov 12 at 6:36
Peter Scott
898615
add a comment |
up vote
1
down vote
favorite
drive.about.get is described by
the revision 20181101 discovery document in which the endpoint for drive:v3.about.get does not include the standard parameters included in the API EXplorer.
V3 is listed as the preferred version.
Given that the fields parameter is required and expects a keyed value from The returned 'about' resource description I expect that this is an erroneous omission from the discovery specification.
Although it is simple enough to work around this, for me it requires additional documentation to explain the requirement.
I note that this is the first Drive endpoint I have explored - I expect that as I continue I will see more missing required parameter specifications. Perhaps this part of the Google Discovery API schema is optional?
My question is - what is the process to help correct this? How frequently are the discovery specs updated and is it up the the user to monitor these changes.
As an additional note for users - you can provide a fields query parameter value of '*' to return all fields. This has also been touched on in Revisions list and get missing information
Any guidance welcome.
google-drive-sdk asked Nov 12 at 6:36
Peter Scott
898615
For any bugs or issues related to the API or incomplete documents try reaching out to their issue tracker same goes for their feature request.
– Mr.Rebot
Nov 13 at 21:19
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
drive.about.get is described by
the revision 20181101 discovery document in which the endpoint for drive:v3.about.get does not include the standard parameters included in the API EXplorer.
V3 is listed as the preferred version.
Given that the fields parameter is required and expects a keyed value from The returned 'about' resource description I expect that this is an erroneous omission from the discovery specification.
Although it is simple enough to work around this, for me it requires additional documentation to explain the requirement.
I note that this is the first Drive endpoint I have explored - I expect that as I continue I will see more missing required parameter specifications. Perhaps this part of the Google Discovery API schema is optional?
My question is - what is the process to help correct this? How frequently are the discovery specs updated and is it up the the user to monitor these changes.
As an additional note for users - you can provide a fields query parameter value of '*' to return all fields. This has also been touched on in Revisions list and get missing information
Any guidance welcome.
google-drive-sdk asked Nov 12 at 6:36
Peter Scott
898615
drive.about.get is described by
the revision 20181101 discovery document in which the endpoint for drive:v3.about.get does not include the standard parameters included in the API EXplorer.
V3 is listed as the preferred version.
Given that the fields parameter is required and expects a keyed value from The returned 'about' resource description I expect that this is an erroneous omission from the discovery specification.
Although it is simple enough to work around this, for me it requires additional documentation to explain the requirement.
I note that this is the first Drive endpoint I have explored - I expect that as I continue I will see more missing required parameter specifications. Perhaps this part of the Google Discovery API schema is optional?
My question is - what is the process to help correct this? How frequently are the discovery specs updated and is it up the the user to monitor these changes.
As an additional note for users - you can provide a fields query parameter value of '*' to return all fields. This has also been touched on in Revisions list and get missing information
Any guidance welcome.
google-drive-sdk google-drive-sdk asked Nov 12 at 6:36
Peter Scott
898615
asked Nov 12 at 6:36
Peter Scott
898615
edited Nov 12 at 15:58
asked Nov 12 at 6:36
Peter Scott
898615
asked Nov 12 at 6:36
Peter Scott
898615
asked Nov 12 at 6:36
Peter Scott
898615
898615
For any bugs or issues related to the API or incomplete documents try reaching out to their issue tracker same goes for their feature request.
– Mr.Rebot
Nov 13 at 21:19
add a comment |
For any bugs or issues related to the API or incomplete documents try reaching out to their issue tracker same goes for their feature request.
– Mr.Rebot
Nov 13 at 21:19
For any bugs or issues related to the API or incomplete documents try reaching out to their issue tracker same goes for their feature request.
– Mr.Rebot
Nov 13 at 21:19
For any bugs or issues related to the API or incomplete documents try reaching out to their issue tracker same goes for their feature request.
– Mr.Rebot
Nov 13 at 21:19
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Thanks to Mr.Rebot for the link to Google's Issue Tracker which is the most valuable part of my objective to find an appropriate channel to pursue Discovery Specification inconsistencies.
The Google Developer API sites haven't led me there and there are quite a few minor quirks in the API Discovery docs I'd like to pursue.
answered Nov 14 at 12:30
Peter Scott
898615
add a comment |
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',
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%2f53256997%2fhow-to-report-errors-in-discovery-v3-specification-required-parameters-missing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Thanks to Mr.Rebot for the link to Google's Issue Tracker which is the most valuable part of my objective to find an appropriate channel to pursue Discovery Specification inconsistencies.
The Google Developer API sites haven't led me there and there are quite a few minor quirks in the API Discovery docs I'd like to pursue.
answered Nov 14 at 12:30
Peter Scott
898615
add a comment |
up vote
0
down vote
accepted
Thanks to Mr.Rebot for the link to Google's Issue Tracker which is the most valuable part of my objective to find an appropriate channel to pursue Discovery Specification inconsistencies.
The Google Developer API sites haven't led me there and there are quite a few minor quirks in the API Discovery docs I'd like to pursue.
answered Nov 14 at 12:30
Peter Scott
898615
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Thanks to Mr.Rebot for the link to Google's Issue Tracker which is the most valuable part of my objective to find an appropriate channel to pursue Discovery Specification inconsistencies.
The Google Developer API sites haven't led me there and there are quite a few minor quirks in the API Discovery docs I'd like to pursue.
answered Nov 14 at 12:30
Peter Scott
898615
Thanks to Mr.Rebot for the link to Google's Issue Tracker which is the most valuable part of my objective to find an appropriate channel to pursue Discovery Specification inconsistencies.
The Google Developer API sites haven't led me there and there are quite a few minor quirks in the API Discovery docs I'd like to pursue.
answered Nov 14 at 12:30
Peter Scott
898615
answered Nov 14 at 12:30
Peter Scott
898615
answered Nov 14 at 12:30
Peter Scott
898615
answered Nov 14 at 12:30
Peter Scott
898615
898615
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53256997%2fhow-to-report-errors-in-discovery-v3-specification-required-parameters-missing%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
For any bugs or issues related to the API or incomplete documents try reaching out to their issue tracker same goes for their feature request.
– Mr.Rebot
Nov 13 at 21:19