Closed caronc closed 6 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
a25ff00
) 99.51% compared to head (cc7a4f2
) 99.52%. Report is 1 commits behind head on master.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Everything seems to work as it should. It's now just adding all of the emoji's into the emojis.py
file.
....This is going to take some time to do... it's a LOT of data entry. If anyone wants to help out, that would be great! :rocket:
Description:
Related issue (if applicable): #649
Emoji support added! :+1:
Emoji's simply translate entries like
:smile:
to :smile: and so-forth prior to thebody
ortitle
being sent upstream.The AppriseAsset holds the global flag of the usage for this new feature. It introduces a new variable called
interpret_emojis
which can be set to the following:None
: Disabled by default, but grant URL over-rides (allow the Apprise URL to contain a?emojis=yes
. This is the default behaviourFalse
: Emoji's can never be applied to the URLs; all emoji processing is disabledTrue
: Emoji's are enabled by default in all cases. Users can however specify?emojis=no
on their URL to cause the processing of that notification to not handle emojis.The CLI has also been updated to add a
-j
or--interpret-emojis
flag. If this isn't specified then the underliningAppriseAsset
takes the value ofNone
(see above for it's definition). Otherwise it is set toTrue
.Translations are based on this link: https://github.com/ikatyang/emoji-cheat-sheet and at the time of doing this PR, i have not added them all yet.
Checklist
flake8
)Testing
Anyone can help test this source code as follows: