feat(triggers): support custom webhook body as requested in #230 #231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to enhance the functionality and documentation of the webhook triggers. The most important changes include updating the documentation to include variable placeholders, adding support for custom webhook bodies, and updating the version number.
Documentation updates:
docs/triggers.md
: Added variable placeholders to the webhook body description and included examples for customizing the webhook body and sending messages to a Telegram channel. [1] [2]Codebase enhancements:
src/lib/components/manage/triggerInfo.svelte
: Added fields for custom webhook body and validation for webhook headers. Added a placeholder for the custom webhook body. [1] [2] [3] [4] [5] [6]src/lib/server/notification/notif.js
: Updated theNotification
class to handle the new webhook metadata structure.src/lib/server/notification/webhook.js
: Modified theWebhook
class to support custom webhook bodies and replace secrets in the body. [1] [2] [3]Version update:
package.json
andsrc/routes/(docs)/+layout.svelte
: Updated the version number from3.0.6
to3.0.7
. [1] [2]