This topic was automatically generated from Slack. You can find the original thread here.
Hi there, what’s the difference between Slack (legacy) and Slack V2?
No practical difference as far as I know, it’s just that Slack V2 uses the app officially approved by Slack. It was made this way to minimize impact on existing connections.
Thanks !
We are currently using the Oauth_key set via the Pipedream Admin panel. Would it be better to continue using the standard slack integration, or should we switch to slack_v2?
, @U03CXTHK4RF
I noticed that slack_v2 is showing some issues when sending Slack messages. We are passing a string, but it seems that it might require using label_value, even when withLabel != True. This puts me in a dilemma regarding whether it’s stable to use the standard slack integration instead of slack_v2, since the old one will eventually be marked as legacy.
Could you also report this issue so that withLabel=True can be properly supported? If I’m mistaken, please update me so I can ensure that we always pass label_value whenever it’s required.
Required to get some clarification of stability of slack_v2 and slack
also about the missing withLable prop case. can we pass as string or Always recommend to pass as _lv when ever it is RemoteProps
Hi , I do not see withLabel used anywhere in either slack or slack_v2. Also, the code is mostly the same in both.
Can you clarify which props exactly you’re having issues with? channelType, conversation or both? And is the issue only occurring in one app but not the other? (couldn’t 100% understand that part)
Yes, thanks !
Actually,
"I passed channelType: "Channels", which worked in the legacy Slack version since both slack versions didn’t declared withLabel: true.
However, in Slack V2, it doesn’t accept plain strings. It only accepts objects in the form channelType: { _lv: { ... } }.
SO it must be have to declared withLabel: true
to know user to please pass value as _lv only
"
According to the GitHub documentation I’ve attached below, from PD they will send withLabel: true if you need the _lv structure instead of a plain string.
Please correct me if I’ve misunderstood anything.
eg: airbnb will required to pass value as _lv so they declared as withLable: true which indicate we must pass value as _lv
Thanks for your response , what error do you get when attempting to use a plain string value like you did in the previous slack app?
If you could share the exact error message / API call you get it on, that’d help a lot