dotCMS / dotCMS/core

dotAI in Block Editor brings back incorrect coding for Headings

Open
#31,577 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Team : Falcon Type : Defect
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

No response

Problem Statement

When using dotAI to populate content in the block editor, it brings back section titles or headers with ### signs or ** signs instead of headings. It should write the section titles as Heading 1 or 2 or 3.

Image

Steps to Reproduce

Go to any content type that has the block editor in it
Create a piece of content, navigate to the block editor and type in /ai to insert dotAI content
Have dotAI write a piece of content that contains sections, like a blog post or report

Acceptance Criteria

Section headers should come back as Heading instead of encoded with stars and pound signs

dotCMS Version

Current

Proposed Objective

Customer Success

Proposed Priority

Priority 4 - Trivial

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the block editor by inserting dotAI content with /ai and including sections such as a blog post or report. Check that section titles are returned as Heading blocks rather than literal ### or ** markers; the acceptance criterion is met when generated headings render correctly.

Written by the indexing model from the issue text.

Assessment

Domain
ai, content, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.