In the Rest v3, I could easily query a commit and get the changed files and patch for each file: https://developer.github.com/v3/repos/commits/#get-a-single-commit
I don't seem to be able to retrieve this info using the new v4 graphQL, does anyone have a clue how?
Currently, it seems that the functionality you are looking for, and much needed in my opinion, isn't supported with GitHub's GraphQL API v4 and it's probably best to stick with the current REST API.
You can refer to the following posts on the official GitHub API support forum and the answers given there by GitHub's staff.
ref1 - 29/5/19
ref2 - 5/11/18
Also, a similar question was posted on SO here
Related
Re golang YouTube API, I would like to know what calls to perform to make a slate image appear in the middle of a livestream. Reading the API documentation here, it's suggested that the "control" operation is used to achieve this, however, this operation is not supported by the API in the latest version. I did find this functionality in a prior version (v0.3.2); why would this have been removed and what is the replacement ?
Cheers,
Saxon
The API behavior you're experiencing is documented officially, as per this excerpt from the official specification of the liveBroadcasts.control API endpoint:
Note: The liveBroadcasts.control method has been deprecated and will stop working on or after 1 October 2020. After that date, all calls to this method will return a forbidden (403) error, and the method will later be completely removed.
Clients can still implement their own slating by adding an overlay to the video sent to YouTube’s ingestion servers. See deprecation announcement.
There's nothing you can do about that, but only to file a feature request directly to Google in the attempt to make the company reinstate the feature that it retracted from the current API.
In my opinion (which is based on the experience of several years of monitoring the SO tags youtube-api, youtube-data-api and youtube-livestreaming-api), waiting for Google to respond to you here on SO is waste of time. Just do what I already recommended you to do in my comments posted under your question above: reach out directly to Google (through the company's official issue tracker site) for to obtain official accounts from the company's staff.
I am in the process of converting our project from the Shopify REST API over to the GraphQL API, however, I can't seem to find a way to pull "Abandoned checkouts".
This is the REST API documentation for abandoned checkouts that I am currently using and referencing:
https://help.shopify.com/en/api/reference/orders/abandoned-checkouts
I can't seem to find the equivalent using GraphQL.
Schema has nothing on that. Probably a better idea to direct your question at Shopify API dev forums. At least there you're bound to get an answer from Shopify, whereas here, you're bound to hear crickets chirping.
When searching in Yammer it uses an /api/v2/search endpoint like this:
https://www.yammer.com/api/v2/search/models?search=test&start=0&size=20&model_types=threads&_network=xxxxxxx&relevance=DEFAULT
Compared to the v1 search endpoint this returns more data. We need this data. And we successfully tested using this v2 endpoint.
Now the question: Is this v2 search endpoint safe to use? Is it "official"? Maybe somebody from Yammer reads along - on their Help page it says:
We encourage you to post all programming questions to StackOverflow
with a #yammer hashtag
So here we are. Any help is appreciated.
The Yammer v2 search API endpoint is not yet officially supported for third-party use. This is because we anticipate the need to make changes to it as we build it out. There are no plans to lock developers out of experimenting with the v2 search API. However, when developing any important functionality against this API, automated testing should be used to detect any unannounced breaking changes that we make while we continue to build it out.
Can you please let me know if the following can still be used? after 4/20:
com.google.gdata.data.appsforyourdomain.generic.GenericEntry;
com.google.gdata.data.spreadsheet.SpreadsheetEntry;
com.google.gdata.data.spreadsheet.SpreadsheetFeed;
com.google.gdata.data.spreadsheet.WorksheetEntry;
com.google.gdata.data.spreadsheet.WorksheetFeed;
com.google.gdata.data.contacts.ContactEntry;
com.google.gdata.data.contacts.ContactFeed;
com.google.gdata.data.contacts.Hobby
I believe these will work after 4/20. Can you please confirm if this needs to be replaced? I checked my jar for contacts and it is using v3.
Spread sheets API v3 and contacts API v3 are available and are not deprecated which are still on gdata. check this link1 and link2.So, you can use the above libraries but you should use Oauth2 as Oauth 1 is deprecated and is not supported by Google after May 5,2015.
I want to gather google analytics data for daily/monthly report. All visitors, visitors for specific path and conversion rate. Setting for google analytics is already done (I think).
I searched ruby libraries, but many informations are out-of-dated and google api is sometimes update.
Now(2012-09-28) what library is popular? And How to get data? I searched ruby-toolbox, but both two libraries are still active?
Libralies
'garb'
https://github.com/vigetlabs/garb
'google-api-client'
http://code.google.com/p/google-api-ruby-client/
Purpose:
My first step: view data
My second step: edit data(Add note or notation)
thanks,
Google-Api-Client works fine, is an official client and is constantly updated, just check the commit logs and you will see. Note that this API is not for Google Analytics only but for any Google API that uses the Google Discovery API. You should try that.
Regardless of the client that you use make sure it's compatible with the latest version of the API. If it's built using the Google API Discovery service it's a plus because that means the client library will have support for new methods as soon as they are available. It's like an API for building API clients.
GARB on the other hand seems to be abandoned for a while and is probably missing out on several features that came recently.
Note that the Google Analytics API are currently read only. So no client library will support that since there's no API for writing annotations. There's a feature request for that though.