Allow hyperlink markdown in webhook embeds fields for name not only value

[incognico]

Please allow hyperlink markdown in the name of an webhook embed field. Currently it only works in the value.

[night]

Can you describe the use case for this? We intentionally exclude links from field titles because they are meant to be headers.

[ftilly]

I believe the use case here would be similar to that of embed link titles.

[incognico]

My use case would be this. Bot posts daily statistics and in my case it would be cool to make the nickname (header) clickable to link the players profile instead of stuffing it into the value field.

Here I also work around it by adding "Weather for:" to the header and put the link into the value.

I don't think there would be any downside in allowing links in the header field, as long as they are indicated as links (blue text).

[night]

I'll leave this open as a feature request, but IMO it would look odd to have some fields with links and others without (due to the crazy contrast link colors have). I would recommend instead using the title and url of the embed to create a header for the embed itself.

[crowlKats]

I have another use case for this:

what you see is results from a search tool for deno modules; i was hoping to be able to add links for the modules to the name of the fields, but then sadly found out that such isnt possible.

[Light7734]

Bump, IMO Embedding links in field's name is extremely useful.

[RheingoldRiver]

We want to use this to show a link to a wiki help text with additional non-contextual help for an embed field. Here are a couple screenshots:

We would really like to link to an additional wikipage further explaining the floor and ceiling notation in addition to our embedded assistance that we already have, but doing so anywhere outside of the field label feels extremely off, and so we are choosing not to link to the documentation at all. This leaves users with less information available to them, but a clearer UI; if we had links in field names available, we could provide the best of both worlds. (The ideal goal is for the shown question mark to be a hyperlink.)

(In particular, we would need to be able to link only PART of the embed field name for this to work.)

[BillyGalbreath]

I, too, would love to be able to use markdown links in embed field headers. I don't understand why a use-case must be justified in the first place, but in my case I am writing a new Jenkins CI bot to post build statuses of build jobs. I'd like to be able to use the commit hash as a field header with a markdown link to the github page of that commit. there can be multiple commits per build, so it makes sense to use the embed fields for this exact purpose. I find it rather disappointing that it's 2023 and this is still being intentionally stripped from field headers.