As for the actual process of building the contract, what works well for me is using API Blueprint-style Markdown in a compatible tool like Apiary, which renders your content into Swagger-like documentation as you type. This way, I and others can mutually "live-scribe" the API contract as we discuss, and seeing it on-screen helps to get people on the same page (and sometimes highlight potential issues that would... Source: about 1 year ago

I’m not sure a JS library qualifies as a PL. Or automation software (SoftStack). Or an API description language. Or a build system. Source: over 1 year ago

Create a Proper API Documentation The following open-source projects can help you with creating documentation for your APIs: APIBluePrint Swagger. - Source: dev.to / over 1 year ago

A common complaint about OpenAPI is that it’s difficult to learn and to read. Consequently, over the years we’ve seen many alternatives to OpenAPI, such as RAML, WADL, API Blueprint, and others. The problem with many of these alternatives is that in most cases they aren’t really more readable or easier to learn. Simpler description languages also tend to support less capabilities for documenting API features.... - Source: dev.to / almost 2 years ago

For the context of this post, only the first task is essential. In it, the team works together to define the API contract. They discuss data format, whether the API will be Rest or RPC, authentication, data compression, and other vital issues. The delivery of this task is the documentation, preferably in a standard like OpenAPI or API Blueprint (my preferred format). - Source: dev.to / almost 2 years ago

I’m not sure a JS library qualifies as a PL. Or automation software (SoftStack). Or an API description language. Or a build system. Source: over 1 year ago

Regarding your first point, a good alternative to Bazel is [Please][https://please.build/] - its build graph can solve exactly this problem in CI. - Source: Hacker News / over 1 year ago

Checkout: https://please.build/ - CMake is not directly supported, but you can easily extend please.build to invoke cmake commands to build your targets. - It does supports both Windows(ehweee) and Linux - MIT - BONUS: it is fast. Really fast(||)! Single binary. It is also versatile. I am using it to build a repo with multiple programming languages(C++(Wasm),Go,Js, Flutter), while spinning up vagrant and... Source: over 1 year ago

> the best way forward is to take the ideas of Bazel (hermetic and deterministic builds) and package them as a good small build system, perhaps even compatible with Bazel so you don't have to rewrite build rules all the time. How does https://please.build measure up? - Source: Hacker News / over 1 year ago

Good luck! I assume you are aware of please.build? Source: almost 2 years ago