You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Some elements containing keywords in name are not well colored #963
When I have enums values like asset only set is colored. FMPOV asset should be colored globaly or not at all.
Swift code samples
Assuming I havz a Swift enum like:
/// Type of icon in an `OUDSTag`
publicenumIcon{
/// The tag has a bullet as icon
case bullet
/// The tag has an image as icon
case asset(Image)}
And the DocC documentation sample like:
/// // Text only with neutral status, for emphasized hierarchy with rounded shape in default size
/// OUDSTag(label: "Label", hierarchy: .emphasized, status: .neutral, shape: .rounded, size: .default)
/// // Or also
/// OUDSTag(label: "Label")
///
/// // Text with bullet and negative status, using default hierarchy (emphasized), shape (rounded) and size (default)
/// OUDSTag(label: "Label", icon: .bullet, status: .negative)
///
/// // Tag with label and icon with image
/// OUDSTag(label: "Label", icon: .asset(Image("ic_heart")))
///
/// // Tag with label and loader, but defined with an image which won't be displayed while loader is active
/// OUDSTag(label: "Label", icon: .asset(Image("ic_heart")), hasLoader: true)
///
/// // If your layout is in RTL model but your tag has an icon with another meaning because of bad orientation,
/// // you can flip the icon
/// OUDSTag(label: "Label", icon: .asset(Image("ic_heart")), flipIcon: true)
For the .asset objects only set is colored in red instead of the whole word or not the word at all.
This visual rendrring is a bit confusing.
Rendering
Both Xcode rendering and web rendering have the issue.
Web page is live here with the rendering below.
Checklist
If possible, I've reproduced the issue using the main branch of this package.
Activity
d-ronnqvist commentedon Aug 26, 2025
Syntax highlighting happens in the renderer
mportiz08 commentedon Aug 26, 2025
Hm. We may be able to fix this with a simple update to the highlight.js syntax highlighting library that we use. I'll need to test that out