I simply took the default simplebody content, added the newly {watcher} placeholder and escaped $ with a second $ as per examples in the documentation.
See the double escaped "\\n" in the logs:
wud | 15:02:09.427 INFO whats-up-docker/trigger.apprise.base: Register with configuration {"url":"https://user:password@apprise.domain.com","simplebody":"Container ${name} running on ${watcher} with ${kind} ${local} can be updated to ${kind} ${remote} \\n ${link}","once":false,"mode":"batch","urls":"m********************************************\n","threshold":"all","simpletitle":"New ${kind} found for container ${name}","batchtitle":"${count} updates available"}
There is indeed less space between each message of updatable container in the batch email I receive.
Should I also have added something so that "\n" does not get escaped or is it really a bug?
I simply took the default simplebody content, added the newly {watcher} placeholder and escaped $ with a second $ as per examples in the documentation.
docker-compos.yml part:
See the double escaped "\\n" in the logs:
wud | 15:02:09.427 INFO whats-up-docker/trigger.apprise.base: Register with configuration {"url":"https://user:password@apprise.domain.com","simplebody":"Container ${name} running on ${watcher} with ${kind} ${local} can be updated to ${kind} ${remote} \\n ${link}","once":false,"mode":"batch","urls":"m********************************************\n","threshold":"all","simpletitle":"New ${kind} found for container ${name}","batchtitle":"${count} updates available"}There is indeed less space between each message of updatable container in the batch email I receive.
Should I also have added something so that "\n" does not get escaped or is it really a bug?