You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use of underscores vs. no underscores is confusing. Especially since using "clientid" instead of "client_id" or vice-versa results in a fun "TypeError" that it can't access 'scope' of object null, which in this case isn't a useful message at all. I would expect both functions to accept the same parameters.
Thanks for reaching out. This bug tracker is intended to report bugs in the Google API JavaScript Client. For support with Google Identity issues, please see https://developers.google.com/identity; if you still need help, ask a question on Stack Overflow under the google-oauth tag.
From scaryg...@gmail.com on April 15, 2014 12:36:16
gapi.auth.signIn({
"clientid": "...",
"cookiepolicy": "...",
"requestvisibleactions": "...",
"callback": "...",
"scope": "..."
});
vs.
gapi.auth.authorize({
"client_id": "...",
"cookie_policy": "...",
"request_visible_actions": "...",
"scope": "..."
}, callback);
The use of underscores vs. no underscores is confusing. Especially since using "clientid" instead of "client_id" or vice-versa results in a fun "TypeError" that it can't access 'scope' of object null, which in this case isn't a useful message at all. I would expect both functions to accept the same parameters.
In addition the documentation at https://developers.google.com/api-client-library/javascript/reference/referencedocs should be enhance to describe gapi.auth.signIn/signOut in addition to gapi.auth.authorize
Original issue: http://code.google.com/p/google-api-javascript-client/issues/detail?id=141
The text was updated successfully, but these errors were encountered: