Request URL (The URL to request when the slash command is run) not receiving anchor link in the text when sent via slash commands
x in one of the [ ])x in each of the [ ])Anchored hyperlink should be sent along with the text i sent
Anchored hyperlink is not sent to my request url, only the text is sent

this is coming to my request url as "this is a link test"
Couldn't find any proper documentation as well with this scenario as well.
Hi @vilvasri-subramanian 馃憢馃徎 thanks for the detailed explanation and steps to reproduce! I'll look into reproducing your issue shortly.
Just to confirm, when you setup the slash command, did enable escaping links?

@mwbrooks
I tried with & without "escaping links" enabled. In both the cases, i cant see the anchored hyperlink
@vilvasri-subramanian Thanks for double-checking the escape setting for me!
I've recreated your issue locally and can confirm that I'm experiencing the same issue.
While recreating the issue, I noticed that the Slack API response does not escape embedded links (like this one). However, it does escape raw links (e.g. https://github.com).
Next up 鈴笍 I'm going to look into whether this is a documentation mistake or a known bug with the Slack API slash command request.
I'll get back to you shortly!
Hey @vilvasri-subramanian - I've looked into this more for you.
Escaping embedded links in Slash Commands is related to the WYSIWYG API change. My understanding is that embedded links are not included, because text is meant to be an approximation of what a user would "see" in Slack.
I've reached out to the Slack API team with a request to escape embedded links, since raw links are escaped. It sounds like it'll be something that will be considered 馃檪
I'd suggest subscribing to the changelog updates to keep an eye out for the fix! The page includes a slash command to deliver the updates into Slack.
@mwbrooks great! thanks for the update Michael. Waiting for the fix!
Hi @mwbrooks
Can you please let me know the update on this issue. When can I expect this to be fixed ?
Thanks!
Hey @vilvasri-subramanian, unfortunately I don't have an update.
In the above thread, I mentioned that we submitted the bug request to the Slack API team. They're aware of the issue and considering a solution.
Unfortunately, that's as far as we can take it. I'd recommend subscribing to the Slack API changelog to be notified of updates and keep an eye out for a fix. If I see it appear on the changelog, I'll update this issue. However, I'd highly recommend that you keep an eye out as well!
hi @mwbrooks
This is still an issue for us. Do you have any update on this?
Thanks.