Your approach seems interesting because it removes some of the barriers to entry for non-technical people.

Yeah, I think even if you are fairly technical it's still pretty hard to manage a growing OpenAPI doc that is good enough to generate clients, sdks and docs from it.

I think that we'll soon be able to help you generate mock clients as well. Probably by generating a first pass with AI and letting you adjust the details manually. This way it could be one-click.

I've bookmarked your blog and will follow along to see what kind of solution you come up with in the end :)

I want to argue: "Well, capitalism contends that someone will show up to offer that product."

"Yeah, we'll get right on that," says the cartel.

These are great suggestions.

I'll write about it the next time I'm in a similar situation.

Great question.

As a consumer, you can set up an alert when any of your API requests has a deprecation or sunset HTTP header. You'd know immediately if any of the APIs you depend on is about to be deactivated.

You're assuming downstream companies will parse & utilize this header

If they were competent enough to do that, they'd probably pay attention to updates sent via, say, email. Brownouts would make people notice, like "oh shit, $API doesn't work!"

I compared three open-source OpenAPI reference generators that work with Express.js almost out of the box.

There are APIs with more than 1,000 paths. However, most have less than 10.

That's a great point, and that's why I explicitly used the word suspicious. If you deploy a new version, then the tool you use to detect suspicious activity should take that into account.

And no, this is not a pitch. I don't work nor am endorsed by any of the services mentioned in the article.

Interesting solution but can't it be achieved with the object-fit CSS property?

Using `object-fit: cover` will make the video resize maintaining its aspect ratio and filling its entire box.

See https://developer.mozilla.org/en-US/docs/Web/CSS/object-fit for more info.

Interesting! It works pretty well except that there's no IE support. So the resizing logic included in the library is useful for projects that need IE10+ support.

You can always use a polyfill like this one: https://github.com/jonathantneal/fitie

Came here to say the same: http://caniuse.com/#feat=object-fit

Working on API Changelog, a service that notifies you whenever any of the APIs you follow changes their documentation:

https://www.apichangelog.com/all

Thanks for sharing, Edward! Please send any feedback.