Skip to content

Make details disclosures easier to spot in rendered markdown

What does this MR do and why?

Make details disclosures easier to spot in rendered markdown

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

Screenshots or screen recordings

Before After
gdk.test_3000_flightjs_Flight_-issues_61__5 gdk.test_3000_flightjs_Flight_-_issues_61
gdk.test_3000_flightjs_Flight_-issues_61__4 gdk.test_3000_flightjs_Flight_-issues_61__1
gdk.test_3000_flightjs_Flight_-issues_61__3 gdk.test_3000_flightjs_Flight_-issues_61__2

How to set up and validate locally

  1. Check out this branch
  2. in the GDK, visit an issue, MR or comment that contains one or more <details> disclosures
  3. If the <details> contains a <summary> then the text of the summary will be bold when the details is open or closed
  4. If the <details> does not contain a summary (rare edge case but valid syntax), then the details text will be bold only when the details is closed. Otherwise the details header text and the contents will not be bolded.

Merge request reports

Loading