added

Owlet Weekly Update (Week of October 19)

Hello and welcome to another edition of the Owlet Weekly Update! Major thanks to our sponsor this week—teenagers! In honor of the teens, we finally get with the times and add node-fetch support to our API Explorer. Read on for this and all of the other #hip features and improvements that were shipped in this release! 🛹

1125

Better recharge those Juuls, kids.

✨ New & Improved

  • As many of you vape-loving, Node.js-using teens out there are aware, the request module is sooooo last year and was officially deprecated this past February. Despite all the time that has passed, the Node.js code samples in the API Explorer still used request… until now! With this major release (version 🎱 of the API Explorer, for those keeping score), we’re finally boarding the node-fetch train. Toot toot! 🚂
  • This release also contains some big improvements to our GitHub Integration. Now, the workflow validates your OpenAPI/Swagger file prior to upload, takes advantage of our wonderful new(ish) API error messages (long overdue, sorry folks!), and includes some new debug logging options which should make troubleshooting a breeze. 🍂
  • As with everything we do here at ReadMe, we're always striving to make our API Explorer as inclusive as possible. Well as of this release, the API Explorer officially supports HTTP headers of all shapes and sizes—in other words, it now preserves casing! See here for a demo. 🔠
  • Have you tried out the api code samples in your reference section yet? Well there’s no better time than the present—this release includes even more improvements on that front. 🚀
  • Good news for documentation that contains a subtle shoutout to ReadMe in the footer—we’ve made a few design tweaks to make the shoutout a little bit more elegant and subtle. 🎨

🛠 Fixes & Updates

  • Some of you were seeing a completely baffling “duplicate key error” message when trying to update your API specification via a PUT request. Major apologies if this caused you to completely question your sense of reality. While I can only partially assure you that this is real life, I can say with confidence that this release includes a much clearer error message (and in case you’re wondering—yes, the error contains a poem). 🖋️
  • As mentioned last week, we made some navigational improvements to our knowledge base! This release includes some housekeeping to make sure that our documentation links are up-to-date. (And if you see any broken links, please let us know!) 🔗
  • Minor bug fixes for projects that downgrade (or upgrade, depending on perspective) to ReadMe Free. 📈
  • Other general stability improvements to the API Explorer. 🔧

Thanks for reading and for being a part of the ReadMe community!

—Kanad and the ReadMe Team :owlbert:

📘

What is the Owlet Weekly Update?

Thanks for tuning in to another edition of our Owlet Weekly Update—an owlet-sized update (posted every Tuesday to the ReadMe Changelog) where we provide an overview of the product updates that went out as part of our new Tuesday release cycle. As we refine our format and process for providing these updates, we'd love to hear what you think at [email protected]!