[Small Feature Request] Add `class` attribute to the `@qualifier` command in the HTML output

[parmi93]

I am trying to achieve something like this:

where the @qualifier Thread-safe has a different background-color than inline.
Unfortunately this is not possible because all qualifiers are rendered as <span class="mlabel">...</span>

I would like to purpose to change this command into something like that:

\qualifier <name> | "(text)" [<label>] --> <span class="mlabel label">name | "(text)"</span>

where <name> | "(text)" is displayed to the user, and <lablel> is used as the value for the class attribute.

[albert-github]

The current syntax is

\qualifier <label> | "(text)"

the proposed syntax is nice but I'm thinking more in the direction of:

\qualifier['{'option[,option]∗'}'] <label> | "(text)"

where option can be a class label.

[parmi93]

I like your proposal, even if the meaning of the single quote characters (') is not entirely clear to me.

Is this how I'm supposed to use this new command?
\qualifier'{'my_class1,my_class2'}' Thread-safe --> <span class="mlabel my_class1 my_class2">Thread-safe</span>

[albert-github]

Nearly, this is indeed how you would use it but without the signal quotes (the '{' sifbals that the '{' is mandatory when using options:

\qualifier Thread-safe --> <span class="mlabel">Thread-safe</span>
\qualifier{my_class1,my_class2} Thread-safe --> <span class="mlabel my_class1 my_class2">Thread-safe</span>

[parmi93]

Thanks for the clarification, I think this new feature might be fine =)

[parmi93]

Maybe I'm asking a bit too much now =)
Would it be possible to add support for the @ref tag when used inside the <lablel> | "text" of the @qualifier command?

What I'm trying to achieve is to create a clickable qualifier, that takes the user to the HTML page where the meaning of Thread-safe is explained, I tried to use the @qualifer command like this, but it didn't work =(

@qualifier "@ref thread_safe \"Thread-safe\""

[albert-github]

\ref Interesting thought but a bit out of scope for this issue, just create another issue for it.

[albert-github]

I've just pushed a proposed patch, pull request #11250