Do not update descriptionHtml if details blocks are changed
What does this MR do and why?
Do not update descriptionHtml if details blocks are changed
In issue descriptions, on each poll, do not update the description html if the only change that happened was that details blocks were opened or closed. This prevents GLFM blocks like GLQL from re-rendering.
Changelog: fixed
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
Screen Recording 2024-09-03 at 13.38.17.mov | Screen Recording 2024-09-03 at 13.37.28.mov |
How to set up and validate locally
- Enable feature flag
:glql_integration
. - Assign yourself some issues.
- Create a few GLQL blocks in
<details>
blocks in an issue description:
<details>
<summary>Details</summary>
```glql
assignee = currentUser()
```
</details>
<details>
<summary>Details</summary>
```glql
assignee = currentUser()
```
</details>
<details>
<summary>Details</summary>
```glql
assignee = currentUser()
```
</details>
<details>
<summary>Details</summary>
```glql
assignee = currentUser()
```
</details>
<details>
<summary>Details</summary>
```glql
assignee = currentUser()
```
</details>
- Save the description.
- Try to open or close the details block. The GLQL block should not re-render
Edited by Himanshu Kapoor