Owlet Weekly Update (Week of June 22nd)
What is the Owlet Weekly Update?
Welcome to the third edition of the Owlet Weekly Update (working title) — an owlet-sized update (posted every Tuesday to the ReadMe Changelog) where we provide an overview of the bug fixes and minor improvements 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]!
Bug Fixes and Minor Improvements
- We've been seeing an issue affecting projects with site-wide passwords where authenticated users were having troubles accessing these projects. Happy to report that this has been resolved! 🔐
- Fixed an issue affecting a small selection of Changelog posts (fortunately this didn't affect the Owlet Weekly Updates... that would have been awkward!) where the body content wasn't loading for logged out users. 📢
- Small usability improvements to our huge Search revamp that we announced a couple weeks ago. 🔍
- Behind-the-scenes improvements to our issue-tracking and release process. 🚀
Bigger Feature Updates and Improvements
As mentioned last week, we released a new NPM module called api
and we just released some huge updates to our API Explorer so you can see this in action! 🎉
Now, there's a new code sample language option available via the OpenAPI Extension called node-simple
. Including this in your OpenAPI file generates Node.js code samples using our api
SDK. You can see this working in the ReadMe API documentation!
Additionally, we also made a few smaller fixes and improvements to the API Explorer:
- Resolved a bug with the way
Content-Type
headers would be interpreted in code snippets so now if theContent-Type
on a request isapplication/json
, the body payloads will be a JSON object, not a stringified JSON object. 📦 - Fixed some issues with the API Explorer not functioning if a server URL in an OpenAPI/Swagger file had a trailing slash. 🔗
- Added support for Cookie parameters across the API Explorer. (See a demo here!) 🍪