-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Slack direct message interpolation doesn't work for $
#11990
Comments
@joscha, would you mind sharing the whole text of your I couldn't seem to reproduce your issue (given to reproduce steps that you provide) |
@vunguyenhung you can see the full text in the screenshot above (except for a sensitive URL which I have masked). Can you try this text? The URL itself without the interpolation containing Update: I also noticed that there is an array access ( |
@joscha Would escaping the backticks like this works for you?
|
Oh, I wasn't aware the back ticks needed to be escaped. Apologies I had missed that they could be an issue. |
@joscha the text shown like this in Slack (given my example)
This is related to Pipedream internals. Maybe @ctrlaltdylan has more context. Hey @ctrlaltdylan, when you have time, could you do a check to see if we can improve this? |
Describe the bug
When using the slack direct message action and using a value from a previous step that has a dollar sign (
$
) in it, the interpolation doesn't work and it throws an errorTo Reproduce
Steps to reproduce the behavior:
Text
field that contains a$
, e.g.{{steps.my_step.$return_value}}
Expected behavior
It should interpolate and THEN send the message further to the Slack API.
Escaping in any way, e.g.
{{steps.my_step.\$return_value}}
doesn't seem to make a difference.I can't actually find the interpolation code in this repository here, it might be closed source as it's part of the product itself.
Given that other interpolations with
{{}}
work, my assumption is that somewhere it doesn't match$
correctly.Screenshots
Setup:
error:
The text was updated successfully, but these errors were encountered: