feat: tags and notifications on PostReportView#42
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Surface
notificationsandtagsonPostReportView, mirroringPostView. Lets consumers (e.g. mod-queue UIs) render report posts through the same components without synthesizing missing fields.notifications: Lemmy v1 reads frompost_actions.notifications(same astoPostView); v0/PieFed default toreplies_and_mentions.tags: defaults to[]everywhere. Lemmy v1 upstream doesn't return tags onPostReportViewyet — tracked at [Bug]:PostReportViewshould include tags LemmyNet/lemmy#6527 (with an explanatory comment inlemmyv1/compat.ts). Internal tracker: PostReportView.tags is always [] for Lemmy v1 #41.Test plan
pnpm lintpnpm test:typespnpm test(23 existing tests pass)notifications/tagsfrom itsPostReportView → PostViewconverter and still typechecks