Fixed posts not opening when clicked from profile feed

[djordjevlais]

no ref

• The click handler was missing

Summary by CodeRabbit

• New Features

  • Improved content interaction handling in profile view modal
  • Streamlined click actions for feed items

• Chores

  • Updated package version to 0.3.52

[coderabbitai]

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/admin-x-activitypub/src/components/modals/ViewProfileModal.tsx

Oops! Something went wrong! :(

ESLint: 8.44.0

ESLint couldn't find the plugin "eslint-plugin-react-hooks".

(The package "eslint-plugin-react-hooks" was not found when loaded as a Node module from the directory "/apps/admin-x-activitypub".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-react-hooks@latest --save-dev

The plugin "eslint-plugin-react-hooks" was referenced from the config file in "apps/admin-x-activitypub/.eslintrc.cjs".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

This pull request involves two primary changes in the admin-x-activitypub package: a version bump to 0.3.52 in the package.json and an update to the ViewProfileModal component's interaction handling. The modification introduces a new utility function handleViewContent that consolidates the click event handling for FeedItem components, simplifying the interaction logic for viewing and commenting on posts.

Changes

File	Change Summary
apps/admin-x-activitypub/package.json	Version updated from 0.3.51 to 0.3.52
apps/admin-x-activitypub/src/components/modals/ViewProfileModal.tsx	Added handleViewContent import and replaced onCommentClick and onClick handlers with unified content handling function

Sequence Diagram

sequenceDiagram
    participant User
    participant FeedItem
    participant HandleViewContent
    participant ViewProfileModal

    User->>FeedItem: Click post
    FeedItem->>HandleViewContent: handleViewContent(post, false)
    HandleViewContent->>ViewProfileModal: Open modal with post content

    User->>FeedItem: Click comment
    FeedItem->>HandleViewContent: handleViewContent(post, true)
    HandleViewContent->>ViewProfileModal: Open modal with comment context

Loading

Possibly related PRs

• Updated profile tab to use dedicated account endpoints in admin-x-activitypub #22010: Updates to profile tab using dedicated account endpoints
• Fixed missing author handle in admin-x-activitypub #22011: Enhances Profile.tsx by adding handle property to author object
• Changed profile modal to always remote load in admin-x-activitypub #22012: Simplifies data structure for ViewProfileModal

Poem

🐰 A rabbit's tale of code so neat,
Version bumped, handlers now complete
Click once, click twice, the magic flows
Through handleViewContent, the wisdom grows
Simplicity hops, complexity fades! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6b9e6b2 and c2b1ec1.

📒 Files selected for processing (2)

• apps/admin-x-activitypub/package.json (1 hunks)
• apps/admin-x-activitypub/src/components/modals/ViewProfileModal.tsx (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• apps/admin-x-activitypub/package.json

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Unit tests (Node 20.11.1)
• GitHub Check: Unit tests (Node 18.12.1)
• GitHub Check: Lint

🔇 Additional comments (2)

apps/admin-x-activitypub/src/components/modals/ViewProfileModal.tsx (2)

19-19: LGTM! Import statement is well-placed.

The addition of handleViewContent import aligns with the PR's objective to fix post click handling.

---

177-178: LGTM! Click handlers properly implemented.

The implementation addresses the PR objective by:

• Adding post click handling via handleViewContent
• Supporting both regular post viewing and comment viewing
• Using consistent handler patterns

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.