Skip to content

fix: use user's emoji picker for quoted/referenced notes#490

Merged
barrydeen merged 1 commit intomainfrom
fix/quoted-note-emoji-picker
Apr 23, 2026
Merged

fix: use user's emoji picker for quoted/referenced notes#490
barrydeen merged 1 commit intomainfrom
fix/quoted-note-emoji-picker

Conversation

@barrydeen
Copy link
Copy Markdown
Owner

Summary

  • Quoted/referenced notes rendered inline via RichContent.QuotedNote were showing the default 17-emoji fallback picker with no custom emoji support, instead of the user's sorted-by-frequency picker used everywhere else.
  • Added resolvedEmojisProvider, unicodeEmojisProvider, and onOpenEmojiLibrary to NoteActions and forwarded them (plus a per-event reactionEmojiUrls) into the nested PostCard/GalleryCard rendered by QuotedNote.
  • Wired the new fields in every NoteActions construction: FeedScreen, ThreadScreen, NotificationsScreen, UserProfileScreen, and Navigation.kt (DM, group DM, group room, hashtag, set feed, article). Providers let the already-remembered NoteActions read fresh StateFlow state on each invocation.

Test plan

  • Open a note that quotes another note in the main feed — long-press the reaction button on the quoted note and confirm the full emoji library opens (custom emojis + frequency-sorted unicode).
  • Repeat in a thread view.
  • Repeat in notifications.
  • Repeat on a user profile feed.
  • Repeat in a DM / group DM / group room / hashtag / set feed / article.
  • React with a custom emoji from the quoted note and confirm it publishes and renders correctly.

Quoted notes nested inside another note were using the default unicode
emoji fallback instead of the user's sorted-by-frequency picker with
their custom emojis. Plumb resolvedEmojis, unicodeEmojis, and the
onOpenEmojiLibrary callback through NoteActions so nested PostCard /
GalleryCard renders in RichContent.QuotedNote pick up the same emoji
state as their parent.
@barrydeen barrydeen merged commit f4c7165 into main Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant