Documented and supported low-level API
See original GitHub issueCurrently, the only documented API is probot run ./app.js
and the methods on robot
and context
objects. There are a lot of good reasons for publishing and documenting low-level APIs (building extensions, embedding probot in other apps, and testing–to name a few). I’d like to see us get to a point where we have a documented low-level API that is semantically-versioned.
TODO:
- Expose methods for creating internal modules #399
- Extract logic from
probot run
into a reusable module
What else?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
DynamoDB low-level API - AWS Documentation
DynamoDB Streams has its own low-level API, which is separate from that of DynamoDB and is fully supported by the AWS SDKs. For...
Read more >Low-level API — MDTraj 1.9.3 documentation
The MDTraj trajectory file objects provide a low-level interface to each of the supported trajectory formats. The high level interface is provided by...
Read more >Low level API - Post Affiliate Pro Support Portal - Quality Unit
Low level API is a set of classes for making requests and processing responses. They can be used to make requests for the...
Read more >Low-level API - Developer Documentation - What is fetch.ai?
However, cosmpy also provides low-level access to the entire Cosmos-SDK, ... But the msgs field needs to support multiple types of messages and...
Read more >An Overview of Low-level, Mid-level (Document), and High ...
DynamoDB offers low level API access, a mid-level DocumentClient, and High level ... The mid-level client is more widely supported than the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can this be closed in favor of https://github.com/probot/probot/issues/599 which is more up to date from our ts update?
I think this is resolved with the latest probot version now. Probot is much more decomposable into Probot modules and the underlying Octokit modules. What’s left is documenting how to “eject” probot if your app outgrows the project scope.
For the time being, feel free to ask any questions here.
With the upcoming v11, I want to build Probot on top of https://github.com/octokit/app.js/, which will make it even more decomposable