Customer StoriesReadMe Blog
Back to All
added

Owlet Weekly Update (Week of January 24)

January 28th, 2022

Hello! I'm coming to you shortly after learning that Rihanna is pregnant so I am physically unable to write an introduction about anything else. Anyways, enjoy this week's Owlet Weekly Update! ☔

👍

We've been rolling out a redesigned docs experience for some time now—check out this page for the details!

The legacy docs style is now deprecated and is not receiving any bug fixes. All changes below are only applicable to the new docs experience (unless otherwise noted). We'll communicate a sunset timeline to any remaining legacy customers soon.

✨ New & Improved

  • As previously mentioned, we’ve been hard at work re-thinking how Enterprise admins distinguish between user roles and how to simplify the process of managing multiple projects at scale. We’ve made some major improvements and our beta is now underway! This release includes even more improvements to this beta. If you're an Enterprise project administrator and you're curious about what we've been working on, we’d love for you to try it out! Drop us a line at [email protected]. 👥
  • Like many of you, we’ve had our eyes on the GraphQL hype train for some time now. Well we’re excited to announce that we’ve officially finally entered the beta for our new GraphQL API Reference! Get the details on everything here. 📈
  • Now here’s a highly anticipated feature—we now render an icon next to each of your search results to distinguish which section of your documentation each result is coming from! 🔍
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️
  • This release includes improved international support for variables and the glossary. 🌏

🛠 Fixes & Updates

  • Our file handling has been vastly improved in the API Reference! Hitting "Try It!" now does a far better job of preserving your file contents in multipart/form-data requests. As part of this, we've also added support for the explode and style parameters within the encoding object for multipart/form-data requests. 🗃
  • Semi-related to the above, we’ve also fixed a few edge cases around query string handling. 🧵
  • This release includes various accessibility improvements to our modals throughout the product! You no longer have to deal with focus trapping issues and you can now consistently escape the modal using the—you guessed it—escape key. ⌨️
  • Good news if you’ve been a bit lazy to write response example values—the API Reference now falls back to displaying the default value as an example if you don’t include any examples. 🍂
  • If your API sends a simple boolean response, we previously used to display something like OK... but as of this release, we actually render the boolean value properly! 🆗
  • This release continues on last week’s response headers sans body work and brings better support to the response examples side of things. ⚽
  • I’ve got 9,007,199,254,740,991 problems but the inability to handle large integers in the API Reference ain’t one—at least as of this release. 💯
  • A few tweaks to prevent some jumpiness when navigating to the Landing Page. 🦘

Hope you're staying safe and healthy! Thanks for being a part of the ReadMe community, folks.

—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 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]!