Explore >> Select a destination
|
You are here 
|
janik6n.net | ||
| | | | |
blog.jpalardy.com
|
|
| | | | | Jonathan Palardy's blog about technology | |
| | | | |
navendu.me
|
|
| | | | | An exploration of continuous delivery workflows for building and managing APIs at scale. | |
| | | | |
code.dblock.org
|
|
| | | | | The OpenSearch API specification is authored in OpenAPI and used to auto-generate OpenSearch language clients. I wanted to know how much of the API was described in it vs. the actual API implemented in the default distribution of OpenSearch that includes all plugins. To do so, I have exposed an iterator over REST handlers in OpenSearch core, and wrote a plugin that rendered a very minimal OpenAPI spec at runtime. All that was left was to compare the manually authored OpenAPI spec in opensearch-api-specification to the runtime one, added in opensearch-api-specification#179. The comparison workflow output a total and relative number of APIs described. | |
| | | | |
localheinz.com
|
|
| | | Since GitHub introduced the automatic generation of release notes, creating releases with release notes has become easier than ever. | ||
