-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
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
[Feature] Render m.sticker events #2122
Conversation
Thanks for the contribution!
Once you mark this as ready for review I'll give it some more thorough review. |
Signed-off-by: Marco Antonio Alvarez <[email protected]>
…d into render_stickers
Signed-off-by: Marco Antonio Alvarez <[email protected]>
…o render_stickers
I'm wondering if showing the timestamp below the sticker would be better, because stickers are quite small and you can't open them, so you'll always get some of it hidden by the timestamp overlay |
Thanks for your contribution @surakin !
Maybe a |
Ah yes, that would do, trying that. |
Signed-off-by: Marco Antonio Alvarez <[email protected]>
@surakin sorry for the bumpy process, but I think it's the actual 1st contribution to be merged in the repo and we're seeing some issues with our CI processes and forks 😓 . Since you made some changes to the previews we now need to update the screenshots, but that's proven to be problematic if it's done locally on your PC, so we use the CI for that. However, I'm not 100% sure on how to proceed when forks are involved. Now that #2141 has been merged, could you either merge or rebase the latest changes in Otherwise, maybe installing the Github CLI and using this command would generate the new screenshots in the uploaded branch:
|
It worked, thanks! There are a lot of extra screenshots, but that's normal, given some issues on how Paparazzi names screenshots. |
Am I the first? Yay me! 🥳 |
@surakin it seems like the CI got stuck after the screenshots were generated and I can't approve it... Could you make some change, like a no-op commit or rebasing the existing content so it's triggered again? |
did that help? |
Yes, it's running now. Thank you again! |
It seems like there are some failing tests in |
Signed-off-by: Marco Antonio Alvarez <[email protected]>
Ups, missed that one. Fixed. |
Signed-off-by: Marco Antonio Alvarez <[email protected]>
Signed-off-by: Marco Antonio Alvarez <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good now, thanks! The Maestro checks won't pass because of GH limitations of CI in forks, so I'll just skip them.
What about codecov? Should I worry about that? (first time I see it) |
No, it's ok. The coverage dropped a bit because a lot of code was added and only some of it could be tested, but it's no big deal. Thanks again! |
Awesome! Happy to help 🥳 |
Render m.sticker events
Closes #1949
Type of change
Content
Added rendering of sticker events (both the event and the reply preview)
Motivation and context
This solves #1949.
I mostly use matrix to talk via whatsapp bridges and this fixes having to switch to whatsapp just to see what sticker someone just sent.
Screenshots / GIFs
Tests
I sent myself stickers using Cinny web and Whatsapp and check them in both the emulator & my own phone
Tested devices
Android 13 & 14
Checklist
Signed-off-by: Marco Antonio Alvarez [email protected]