You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
I think there should be a better way to specific the webhook used in a template, or rather, a template should not have a webhook defined in it. This should be more generic to be reusable.
Use Cases
Looking at this config I think highlights the issue even tho this example is quite simple, for bigger and larger templates it might become less easy to maintain.
This means, if I want to sent the same message, to 2 different channels, I simply have to duplicate the entire thing.
If I want to send it to 10 channels I have to duplicate 10 times the same thing.
If I then simply want to change the message, I have to change it 10 times because it's not generic.
For this case, I believe we should have to duplicate the service, since it's a different URL for each channel, but for the template we should be able to specify the same template to be used by any service essentially.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
I think there should be a better way to specific the webhook used in a template, or rather, a template should not have a webhook defined in it. This should be more generic to be reusable.
Use Cases
Looking at this config I think highlights the issue even tho this example is quite simple, for bigger and larger templates it might become less easy to maintain.
This means, if I want to sent the same message, to 2 different channels, I simply have to duplicate the entire thing.
If I want to send it to 10 channels I have to duplicate 10 times the same thing.
If I then simply want to change the message, I have to change it 10 times because it's not generic.
For this case, I believe we should have to duplicate the service, since it's a different URL for each channel, but for the template we should be able to specify the same template to be used by any service essentially.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: