From 9c65b823b38ae35f05d53e31abb846312ff78cc9 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Sun, 1 Oct 2023 09:45:22 -0400 Subject: [PATCH] Updated Development_Contribution (markdown) --- Development_Contribution.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Development_Contribution.md b/Development_Contribution.md index b494363..aa1b1c6 100644 --- a/Development_Contribution.md +++ b/Development_Contribution.md @@ -200,8 +200,7 @@ With respect to the above example: If your service is really complex (and requires a lot of code), maybe it's easier to split your code into multiple files. This is how i handled the [NotifyFCM plugin i wrote](https://github.com/caronc/apprise/tree/master/apprise/plugins/NotifyFCM) which was based on Google's version. - Don't be afraid to just copy and paste another already created service and update it for your own usage. - - [plugins/NotifyJSON.py](https://github.com/caronc/apprise/blob/master/apprise/plugins/NotifyJSON.py) is a simple reference you use (not too complicated). - - [plugins/NotifyGitter.py](https://github.com/caronc/apprise/blob/master/apprise/plugins/NotifyGitter.py) is a bit more complicated, but introduces an upstream API interface with attachments. + - [plugins/NotifyJSON.py](https://github.com/caronc/apprise/blob/master/apprise/plugins/NotifyJSON.py) is a bit advanced; but shows the general idea of the structure. - [plugin/NotifyFCM](https://github.com/caronc/apprise/tree/master/apprise/plugins/NotifyFCM) is a much more complex design but illustrates how you can build your notification into smaller components. - All in all.... just have a look at the [plugins directory](https://github.com/caronc/apprise/tree/master/apprise/plugins) and feel free to use this as a reference to help structure and solve your own notification service you might be building