Tim Reddehase d517f786ef Allow slashes in receivers (#2011) ... * do not split receiver by slash I'm not sure why this was originally done, because a slash seems to be perfectly valid in a receiver definition. The only issue i encountered was that linking from a fired alert was not working, because of the splitting performed here. Signed-off-by: Tim Reddehase <tim.reddehase@xing.com> * urlquery escape Receiver by default for URL If Receiver is allowed to contain slashes and other special characters we need to percent encode them properly. Signed-off-by: Tim Reddehase <tim.reddehase@xing.com> * rerun make asset/assets_vfsdata.go Signed-off-by: Tim Reddehase <tim.reddehase@xing.com>		2019-08-28 10:01:47 +02:00
..
default.tmpl	Allow slashes in receivers (#2011)	2019-08-28 10:01:47 +02:00
email.html	Email is green if only none firing (#1475)	2018-07-23 14:06:46 +02:00
template_test.go	Add fingerprint to expected template test output (#1968)	2019-07-23 09:57:24 +02:00
template.go	Allow slashes in receivers (#2011)	2019-08-28 10:01:47 +02:00