Skip to content

chore: Rename gl-markdown styles to duo-chat-markdown and adapt duo-chat usage

Jannik Lehmannrequested to merge
jnnkl-duo-chat-md-default-styles into main

What does this MR do?

chore: Rename gl-markdown styles to duo-chat-markdown and adapt duo-chat usage

Renamed gl-markdown styles to duo-chat-markdown and updated DuoChat components to use the newly named styles. Removed the now unused gl-markdown styles.

The GlMarkdown component is mostly unused, with DuoChat being the only component that partially relies on it. This MR isolates the necessary styles from GlMarkdown into the DuoChat component and removes the unused gl-markdown styles from the codebase. This cleanup improves maintainability by reducing unnecessary dependencies and ensuring that DuoChat uses only the required styles.

Discussion where this came up: #2712 (comment 2161483470)

Screenshots or screen recordings

No visual changes, reproduce on: http://localhost:9001/?path=/docs/experimental-duo-chat-duo-chat-message--docs

Integration merge requests

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Jannik Lehmann

Merge request reports