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.
Description:
Related issue (if applicable): #649
Emoji support added! 👍
Emoji's simply translate entries like
:smile:
to 😄 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: