Separate Text Description and the Markdown Overview Description in Publisher Portal

[AqeelMuhammad]

Purpose

This pull request separates the text description and the markdown overview description in the publisher portal.

Problem

When API descriptions are saved as markdown, they are stored as documents. As a result, fetching the API description through product APIs requires at least three API calls, making the process inefficient. Additionally, returning NULL for the description in the API response.

Approach

• Separate Text Description and Markdown Content
• Add a new text input field named "Description" under Design Configurations -> Portal Configurations -> Basic Info
• Replace the "Edit description" button with a "Edit overview markdown" button linking to the markdown content of the API
• When a user saves changes after adding markdown for the first time, create a new document with otherTypeName as _overview
• To remove the markdown overview, clear the content and save changes. It will delete the _overview document

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud