From 5cafc1df0c076077d8b1298a61d3292abcd97edf Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Mon, 13 May 2024 21:25:12 -0400 Subject: [PATCH] Updated Development_Contribution (markdown) --- Development_Contribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Development_Contribution.md b/Development_Contribution.md index f1bb44c..2f58638 100644 --- a/Development_Contribution.md +++ b/Development_Contribution.md @@ -196,7 +196,7 @@ With respect to the above example: Any other functions you want to define can be done to you hearts content (if it helps with organization, structure, etc) Just avoid conflicting with any function written in `NotifyBase()` and `URLBase()` - 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. + 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/fcm) 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/custom_json.py](https://github.com/caronc/apprise/blob/master/apprise/plugins/custom_json.py) is a bit advanced; but shows the general idea of the structure. - [plugin/fcm](https://github.com/caronc/apprise/tree/master/apprise/plugins/fcm) is a much more complex design but illustrates how you can build your notification into smaller components.