extern/apprise
1
0
Fork 0
mirror of https://github.com/caronc/apprise.git synced 2024-12-04 22:11:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Development_Contribution (markdown)

Chris Caron 2024-05-13 21:25:28 -04:00
parent 5cafc1df0c
commit 9d52d57551
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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/fcm) 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 [FCM 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.