feat: eXIP7.3.0.19 Post Reporting EXO-89953 - #909
Conversation
boubaker
left a comment
boubaker
left a comment
There was a problem hiding this comment.
AI review — Round #1 (feature/mips integration)
Reviewed as part of the Post Reporting delivery (Meeds-io/social#6063, Meeds-io/analytics#440, exoplatform/data-upgrade#306), against the eXip note (resynced 2026-08-31, content now in Repositories touched) and board tasks US01 (89471) / 89932. Cherry-picks of #902 + #906 verified patch-identical with feature/devx. One 🟡 anchored inline.
Previous rounds (content#902 Round #1–#2), re-verified at 05cd8a2
| Item | Status |
|---|---|
🟢 beforeDestroy re-registered the extension listener |
✅ still fixed (removeEventListener) |
| 🟢 Articles reportable only from the stream-hosted view | ➖ now a recorded Out of scope decision in the spec's Ledgers (PO, 2026-08-31) — closed |
#906 placement: the Report item now sits immediately before Delete, matching the PO's US01 rejection and the social menus' rank: 90.
Verified conform: the explicit stale-flip fires on CONTENT_AND_TITLE updates only, with both directions pinned (testContentEditMarksArticleReportsStale / testNonContentEditKeepsArticleReportsActive) and the in-place comment stating why the article path needs the explicit delegation (its activity update is broadcast=false); ActivityReportService injected required = false with a null guard, valid here because content compiles against the social artifact (the BOM already implies it — the ASM-metadata @ConditionalOnClass guard of the badge pattern is for contributors that may run without the host, which is not this case); menu entry driven by the server-derived booleans only; activity-reported sync with the post/comment discrimination handled.
Classification: N3 taken alone (additive UI + a service-to-service delegation, no REST/DAO/schema/ACL surface); the delivery as a whole is N1 via social#6063 — max-severity aggregation applies at the feature/mips integration; its approver must know that, no auto-merge on AI review alone.
🤖 Generated with Claude Code
147ea54 to
1915baf
Compare
#902) Adds the Report entry to the news article detail menu, driven by the activity's server-derived canReport/hasReported flags threaded down from the hosting activity view, with live state sync after reporting. Content edits (title/body) reset existing reports; posting/publishing/categories updates keep them active.
…O-89471 (#906) PO feedback on task 89471 (US01, tested and not validated): the design places the Report action immediately before Delete in the contextual menu — same fix as the activity/comment menus in Meeds-io/social (see the sibling PR). The Report block moves after the menu extensions, right above the Delete entry; its behavior is unchanged (pure move, +16/-15). Follow-up of #902 (merged). Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…XO-89932 Integration review finding: the article menu only toggled the disabled class with an aria-label - colors unchanged and no visible tooltip. Mirrors the stream menus treatment (tasks 89474/89932): a v-tooltip whose activator is a wrapper element (the disabled item blocks pointer events), and the text-disabled-color utility class on the icon and label when reported. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2 participants
Integration of the Post Reporting eXip (eXIP7.3.0.19) from feature/devx — this repo's delivery commits cherry-picked in their original order (#902, #906), verified patch-identical.
Knowledge: carried by the social integration PR.
Classification: the delivery is N1 via social (max-severity aggregation).