We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The issue tinode/tinode-js#74 suggests that each character of string must be treated as grapheme.
index-dev.html
index.html
On server, ensure that push notification adapter is turned on(fcm or tnpg). Considering preview length: 5 Two ways to reproduce:
Hi 🏴🏴 🏴🏴
Push notification sent has wrong text when parsed through drafty.Preview and drafty.PlainText
Push notification text content should be equal to Hi 🏴🏴
Hi 🏴🏴
Push notification text content should be equal to Hi 🏴
Hi 🏴
The text was updated successfully, but these errors were encountered:
refactor: tinode#904 rectify drafty test file
5181939
refactor: tinode#904 should reset iterator only once
d53261d
Merge pull request #905 from dilshans2k/bugfix/drafty-should-correctl…
e3a9d31
…y-parse-message-content-for-push-notification fix: #904 drafty should correctly parse message content for push notification
b776e3c
No branches or pull requests
Subject of the issue
The issue tinode/tinode-js#74 suggests that each character of string must be treated as grapheme.
Your environment
Server-side
Client-side
index-dev.html
to reproduce the problem, notindex.html
.Steps to reproduce
On server, ensure that push notification adapter is turned on(fcm or tnpg).
Considering preview length: 5
Two ways to reproduce:
For eg:
Hi 🏴🏴 🏴🏴
Push notification sent has wrong text when parsed through drafty.Preview and drafty.PlainText
Expected behaviour
Push notification text content should be equal to
Hi 🏴🏴
Actual behaviour
Push notification text content should be equal to
Hi 🏴
The text was updated successfully, but these errors were encountered: