[Bug] Legacy WebHook Slack Migration

[ordonezgs]

WME-send-to-slack/WME-send-to-slack.user.js

Lines 538 to 555 in 8d6472a

	if(key.toLowerCase() == "slack")
	{
	$.ajax({
	data: 'payload=' + JSON.stringify({
	"text": TextToSend,
	"username": ScriptName + " " + GM_info.script.version,
	"mrkdwn": true,
	"channel": serverDB[localStorage.getItem('WMESTSServer')][key]["chanel_" + chanel],
	"icon_emoji": actionicon
	}),
	processData: false,
	type: 'POST',
	url: serverDB[localStorage.getItem('WMESTSServer')][key][chanel],
	error: function(x, y, z)
	{
	log('Slack error : ' + x + ' ' + y + ' ' + z);
	}
	});

Not sure if the script is working well in Slack, because of this documentation talking about:
You cannot override the default channel (chosen by the user who installed your app), username, or icon when you're using Incoming Webhooks to post messages. Instead, these values will always inherit from the associated Slack app configuration.

Please check Legacy Docs:
https://api.slack.com/legacy/custom-integrations/incoming-webhooks
and Up-to-Date Slack WebHook Documentation:
https://api.slack.com/messaging/webhooks

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[tunisiano187]

Yes it works correctly, that's just the only solution to have the same webhook everywhere. It can be a webhook by channel, but currently it works perfectly that way. Le jeu. 23 juil. 2020 à 00:31, issue-label-bot[bot] < notifications@github.com> a écrit :

…

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback! Links: app homepage <https://github.com/marketplace/issue-label-bot>, dashboard <https://mlbot.net/data/tunisiano187/WME-send-to-slack> and code <https://github.com/hamelsmu/MLapp> for this bot. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOQG6ZWDCSO6Z5CTLBADZ3R45SEZANCNFSM4PFFBLPA> .