added
Owlet Weekly Update (Week of April 18)
April 22nd, 2022
Hello and welcome to another weekly update, y'all! This week we're adding onto our Search API and making lots of enhancements and fixes to our API Reference. More below! π΅οΈ
β¨ New & Improved
- Our new editor is right around the corner, yβall! This release includes even more work on that front. You can get a sneak peek inΒ our discussion forumsβif you want to be a part of our beta, drop us a line! βοΈ
- When using "Try It!" with
GET
endpoints in the API reference, you previously may have seen a response that's been cached in your browser, even if the response code appears to indicate otherwise. With the caching changes in this release, users will always see the freshest response from the server, along with the correct status code. β² - This release includes various improvements to our Python code snippets in the API Reference! HTTP accessors are more readable and file uploads look much cleaner. π
- Weβve added Recipes to the results returned from our Search docs endpoint. π
π Fixes & Updates
- Fixed an issue where endpoint pages in the API reference that were missing response objects that were missing Schema objects would crash. π₯
- Fixed an issue in the API reference where the base URL in your API log would sometimes be prefixed with a
https://try.readme.io/
. Whoops. π - This release fixes an issue where long JSON responses would occasionally get cut off and show up on a single line. π€₯
- Fixed an issue affecting a small chunk Enterprise projects where certain search result links were broken. π
- Fixed various UI issues in the dashboard and the API reference. ποΈ
Hope you're staying safe and healthy! Thanks 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]!