v0.1.85 — 15 Jul 2026
Bug Fix — Rich Text Markdown field now stores real Markdown
Who is affected: Anyone using the Rich Text Markdown field interface in Platform Studio content forms.
What was wrong
Although the field is a Markdown interface, it saved the editor’s HTML into the field value, so “Markdown” fields actually stored HTML — and values that already contained Markdown were not rendered when loaded back into the editor. In addition:
- The toolbar’s Insert Table dropped literal pipe-syntax text (
| Header | Header |) into the WYSIWYG document instead of creating a real table. - The Preview mode was a read-only render of the editor’s HTML, not a Markdown preview.
- Pasting content copied from a rendered Markdown code fence (GitHub, chat apps, code viewers) trapped the entire document in a single code block.
What changed
The component is synced to Buildpad UI rich-text-markdown 1.9.1:
- Markdown round-trip: the field value is parsed as Markdown on load and serialized back to Markdown on every change, so the stored value is always real Markdown.
- GFM tables: Insert Table creates a proper editor table that serializes back to Markdown pipe syntax, with table styling in both the editor and rendered output.
- Source view: the read-only Preview mode is replaced by an editable monospace Source view of the raw Markdown. The WYSIWYG editor renders formatting live, so it doubles as the preview. The
previewFontprop is deprecated and has no effect. - Smart paste: content copied from a rendered Markdown code fence is re-parsed as Markdown instead of becoming one giant code block; genuine code snippets still paste as code blocks.
| Scenario | Before | After |
|---|---|---|
| Saving a Markdown field | ❌ Stored HTML | ✅ Stores Markdown |
| Loading a value containing Markdown | ❌ Raw syntax shown as plain text | ✅ Rendered in the editor |
| Insert Table from the toolbar | ❌ Literal pipe-syntax text | ✅ Real table, round-trips as GFM |
| Pasting from a rendered code fence | ❌ Whole document trapped in a code block | ✅ Parsed as Markdown |
Feature — Logs pagination and load more button
Who is affected: Platform Studio administrators and users viewing application logs.
What was wrong
When checking logs in Platform Studio, all logs in the database were loaded at once. For environments with many logs, this caused performance and UI rendering delays, with no limit or paging to manage the volume.
What changed
Pagination has been implemented on the application logs page.
- Initial view: Only the first 10 logs are displayed.
- Load more: A centered “Load more” button appears to load and increment the visible logs count by 10 logs per click.
- Auto-reset: The pagination count is automatically reset when logs are cleared, re-fetched, or when filters/search keywords are modified.
- Total summary: The footer count summary is updated to clearly show the current visible logs count relative to the total number of logs.
Improvement — Application logs sorted from newest to oldest
Who is affected: Anyone checking logs in Platform Studio.
What was wrong
Logs were previously displayed sorted in a less intuitive order by default, and prepending streamed logs from SSE while maintaining proper ordering was complex due to client-side reversing of the initial API payload.
What changed
The UI now displays logs sorted from newest to oldest. We removed client-side reversing of the API payload and prepended new incoming SSE (Server-Sent Events) stream logs directly. This ensures the most recent log entries are always shown at the top immediately.