May 28th Release

• Reduced rendering delays
• Improved load times and responsiveness across devices and browsers

• Optimized key user flows, reduced API payload sizes, and improved responsiveness
• Faster interaction across analytics and project views

• Enhanced performance in large documents
• Reduced lag and improved editing fluidity through better state management and rendering efficiency

We’ve resolved an issue where importing certain links into the Theneo platform resulted in an error: "The format or scheme of the text is not supported."

What’s fixed:

• The platform now better handles various link schemas.
• Users will see improved validation and clearer guidance when providing unsupported formats.

Switching between Editor and Preview Mode no longer collapses the navigation menu.

What’s improved:

• The left-side navigation menu now retains its expanded state after returning from Preview Mode.
• The selected section remains highlighted for better continuity and user experience.

We’ve resolved a issue affecting the Plain Text option in code blocks within the published view:

• Light Mode Fix: Plain Text content inside code blocks is now clearly visible in light mode, ensuring proper contrast and improved readability for users viewing documentation across different themes.

Previously, converting the first section into a header with no subsections caused a crash in Single Page mode.

Now resolved:

• You can safely convert headers regardless of their structure, without crashing your project.

A subtle but impactful bug was fixed where numeric values of 0 were incorrectly shown as null in the published view.

Now working as expected:

• 0 is displayed correctly when explicitly entered.
• Empty number fields still show null.

We’ve resolved multiple parsing issues affecting GraphQL specs:

• Deprecated Fields: Fields marked with @deprecated are now correctly shown with the appropriate label and tooltip.
• Enum Arrays: Enum values defined as arrays are now properly parsed and displayed.

We fixed a widget conflict where the Insert Link function didn’t work inside a Card widget if it was in the same section as an API Request widget.

Now you can:

• Seamlessly add links in Card widgets, regardless of other widgets in the same section.