When I view an epic in the ZenHub dashboard, I can see the issues which relate to an epic. It seems these can be added/removed using the REST API described here:
https://github.com/ZenHubIO/API#add-or-remove-issues-to-epic
Is there also an REST API which allows for the retrieval of the epic issues?
It seems the GraphQL API described here is a little more feature rich but I was unable to locate the reference documentation which describes the query I am looking for. It appears that the Explorer feature could be used to locate the right schema information, but it seems this is not available on ZenHub Enterprise?
Related
Moodle is a platform for creating training and educational material. By default, it is possible to make the content by clicking on controls.
GitHub is a place for version management and teamwork.
Question: I wondered if there is a way to (programmatically) populate/update a Moodle training from a GitHub repository. Does Moodle offer an API that would allow the implementation of such a functionality?
Idea:
The GitHub repository contains mark-down files in a specific format and folder structure.
Yes. Theoretically. Moodle offers an API (https://docs.moodle.org/dev/Web_service_API_functions) through which you can update courses along with much other functionality.
You would have to write the script yourself, of course. I've been briefly looking in to this as well, but the moodle webservice API is not intuitive and is underdocumented. There's been talk of making a more sensible, RESTful API (https://tracker.moodle.org/browse/MDL-49607) but it doesn't seem to have gotten anywhere.
Is it possible to create a BotPress bot entirely using the API? More specifically, can I accomplish most of all of what I would do in the UI by just using API methods? I looked, and I don't see a createBot() method, so I'm wondering if this is possible.
Second question, I read that multi-tenant support has been added in version 11. Is there any documentation on how this works?
Yes this is possible, if you use the F12 on your browser to see how Botpress works under the hood. you will find that it uses some API.
Here are some I found and used :
Bots management: /api/v1/admin/bots
QNA management: /api/v1/bots/{botid}/mod/qna/questions
Managing a specifi bot: /api/v1/admin/bots/{botid}
...
Keep looking and you will find more than that.
I know WebkitSpeechRecognition is only available on the chromium browser. However I am wondering how it converts the voice into text?
I tried to monitor the network log from developer console on the Google Chrome and I don't see any network activity. I thought I would send API request to the Google but I really don't.
I cannot find any architectural document on this either.
Does any one has any idea?
to my knowledge, there is no official documentation for the Google Speech API that is used in Chromium, but it has been "reversed engineered" by inspecting Chromium's source code
when you search for it, you should find multiple blogs / tutorials that describe, how the REST API can be used
a good description on how to use it, can be found here
http://blog.travispayton.com/wp-content/uploads/2014/03/Google-Speech-API.pdf
(with regard to the description in the PDF: the mentioned "Speech API V1" is deactivated by now, so only the "Full-Duplex API" can be used)
But note, that you need an API key via Google's Developer Console (for the Speech API); and for that you need to be registered in the Chromium Development Group.
Also, using your own key, as of now, the Speech API it is limited to 50 transactions per day.
I noticed the Watson API for Personality Insights that can visualize the profile in a cool D3.js chart has been deprecated. What are the plans to support this going forward?
Instead of an API, we have made it available as a client side library. Its available in the sample application code: https://github.com/watson-developer-cloud/personality-insights-nodejs .
"The visualize API is now deprecated and will be removed entirely in a future release. You can use the personality.js JavaScript file that is provided with the sample application to achieve similar results from the client. The textsummary.js JavaScript file provides additional formatting for the results of the service"
We're currently using MarkLogic's dls functions to handle document versioning, and are trying to switch over to use the REST API. The document endpoint doesn't use versioning by default, and I can't figure out a way to get it to. I'm referring to the dls functions for keeping multiple document versions, btw, not the new "content versioning" the REST API documentation mentions. In fact, the only reference to document versions in the REST API docs seems to be a line saying that content versioning isn't the same thing.
The only solution we've been able to come up with is to write a custom endpoint that duplicates everything the existing document endpoint's PUT does, plus document management. I'd rather avoid that if possible, especially when looking at MarkLogic 7's partial document updates. We're using MarkLogic 6 now, if it matters, but it doesn't look like 7 has any new features related to this.
Is there a way to do this using MarkLogic's existing endpoints?
You can write a REST API extension that automates the DLS operations. See http://docs.marklogic.com/guide/rest-dev/extensions. You will largely end up duplicating a lot of the same things, but this will plug into the existing endpoints.
Yes, MarkLogic 7 added content versioning to make refreshing of caches easier. And unfortunately, the DLS library hasn't been integrated into the REST api so far. You can file a feature request at support if you like.
In the mean time, the best suggestion I can give is use a separate route to do document updates using DLS (your current route or a limited custom endpoint that only supports the DLS functions you need for doc updates), and do anything else (as far as possible) using the existing REST api. You can look at this other stackoverflow question to see how to limit searches to the latest doc versions:
Marklogic REST API search for latest document version
HTH!
A member of MarkLogic has put together a REST extension to provide better DLS support in the REST-api. Hopefully that makes working with DLS over the MarkLogic REST-api a lot easier:
https://github.com/sanjuthomas/marklogic-dls-rest-extension
HTH!