Owlet Weekly Update (Week of August 9)
Hello and welcome to another Owlet Weekly Update, friends! In summary (yes, that is in fact a pun), we're bringing lots of little fixes and improvements in the API reference section along with some behind-the-scenes improvements to Documentation Metrics. Details below! 🚀
We've been rolling out some new docs designs for a little while now—check out this page for the latest details on what's going on! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.
✨ New & Improved
- Behind-the-scenes improvements to Documentation Metrics—in other words, faster loading times when viewing Page Quality in the dashboard! 📈
- 🆕 As of this release, the
summaryfield now renders for request and response examples! ∑
🛠 Fixes & Updates
- 🆕 In previous updates, we've mentioned the massive accessibility gains that come with our new documentation design—one of which is a "Jump to Content" button when tabbing through the page! This release fixes some styling issues that we were seeing for a small subset of project styles. 🎨
- 🆕 Don't you hate to be perceived as something when you're actually something else? While we're unable to address the immense societal expectations that are constantly thrust upon us, this release addresses issues where JSON response examples was being perceived as strings and vice versa. 🔮
- 🆕 This release includes better support for optional OAuth2 securities. And by that, I mean the page will actually load for OpenAPI definitions that utilize them. 🔒
- 🆕 Fixed an issue where setting certain parameter defaults to
nullwould cause rendering issues. 🥴 - 🆕 Addresses several rendering edge cases for schemas that utilize polymorphism. 🥞
Thanks for reading and for being a part of the ReadMe community, folks!
—Kanad and the ReadMe Team 
What is the Owlet Weekly Update?
Thanks for tuning in to another edition of our Owlet Weekly Update—an owlet-sized update (posted every week to the ReadMe Changelog) on the product updates we're shipping here at ReadMe. We'd love to hear what you think of these updates at [email protected]!