openapi-devtools VS elements

Not specific to the CPG realm, but I've had some very good luck working with the OpenAPI-devtools Chrome Extension[1] (previous discussion here on hackernews[2]) to discover the underlying APIs of various sites that I want to scrape data from.

[1] https://github.com/AndrewWalsh/openapi-devtools

[2] https://news.ycombinator.com/item?id=38012032

As a follow up, the algorithm that powers this makes use of the chrome.devtools.network API. Specifically it passes the Request object that is in the HAR 1.2 archive format.

So if you can pass the equivalent of that in Firefox/other browsers to the insert method and switch things up a bit, it should be relatively straightforward. I will think about pulling out the core logic into its own lib.

https://developer.chrome.com/docs/extensions/reference/devto...

https://developer.chrome.com/docs/extensions/reference/devto...

https://github.com/AndrewWalsh/openapi-devtools/blob/main/sr...

Looks like a similar solution to https://github.com/stoplightio/elements - will give this a whirl some time!

Complete, up-to-date, and exhaustive documentation that can be generated with Stoplight Elements

An update to the OpenAPI configuration and support for Stoplight Elements

Starlite has substantially enhanced OpenAPI (3.1) documentation - in fact, its the most complete autogenerated schema around, and it ships with Redoc, Swagger-UI and Stoplight-Elements static sites.

Stoplight Elements 🆓 / Stoplight

An issue emerged in our library integration that made us challenge our belief that our dependencies are under control. In short, our app crashed because of a bug in a dependency’s dependency. Despite fixing the nested dependency, the issue remained to be unsolved.