April 18th Release
1. API Versioning Enhancements:
- Seamless Version Switching: Users can now effortlessly switch API versions directly from the API Explorer and Changelog pages, as well as from mobile devices. We have introduced an intuitive API versioning dropdown for smoother interaction and navigation.
2. Bug Fixes for Improved Functionality:
- API Documentation Navigation Fix: Previously, users encountered an issue where the "Open in API Reference" link within the API Explorer failed to redirect them to the specific section of the API documentation. This bug has been successfully resolved, ensuring smoother navigation and quicker access to relevant documentation.
- Editor Enhancements: We've addressed a couple of issues within the editor:
- API Collection Name Update: Previously, the option to update the API collection name within the editor was non-functional. This has now been rectified, allowing users to effortlessly update collection names as needed.
- Nullable Parameter Toggle: Users experienced difficulties marking parameters as nullable due to a malfunction in the nullable toggle within the editor's parameters additional properties settings. This issue has been fixed, streamlining parameter management within your API projects.
3. Content Type Support Expansion:
- Support for application/x-www-form-urlencoded: We've added support for the urlencoded (application/x-www-form-urlencoded) content type. This option will now be visible in the editor as a pickable option, and its behavior has been optimized within the API Explorer.
How to Use: When creating or editing API requests, simply select "Accept-Encoding" from the available content type options. Your data will then be encoded accordingly for transmission.
4. Access Management Improvement:
- Private Sections Visibility Fix: An issue was identified where sections designated as private using the Theneo Access Management feature were not visible in the publish view for editors, even when proper authorization was granted. This problem has been addressed, ensuring that authorized users can access private sections as intended.
Was this section helpful?
What made this section unhelpful for you?
On this page
- April 18th Release