[PWA-5] fix: PWA sticky issue comment

[anmolsinghbhatia]

Changes:

This PR includes following changes:

• Added a sticky comment section in the PWA for both the issue peek overview and issue details pages.

Reference:

[PWA-5]

Summary by CodeRabbit

• New Features

  • Improved styling for the issue comment creation component based on the state of the issue detail, enhancing user interface responsiveness.

• Bug Fixes

  • Resolved visual inconsistencies related to the display of comments in the issue detail view.

[coderabbitai]

Walkthrough

The changes involve modifications to the IssueCommentCreate component in the comment-create.tsx file. An import for the cn function from common.helper is added to enable conditional CSS class application. This is driven by the state of the peekIssue variable obtained from the new useIssueDetail hook, allowing for dynamic styling based on the issue detail state.

Changes

File	Change Summary
web/core/components/issues/issue-detail/issue-activity/comments/comment-create.tsx	Added import for cn function; integrated useIssueDetail hook; applied conditional CSS class based on peekIssue state.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant IssueCommentCreate
    participant useIssueDetail
    participant common.helper

    User->>IssueCommentCreate: Render component
    IssueCommentCreate->>useIssueDetail: Retrieve peekIssue
    useIssueDetail-->>IssueCommentCreate: Return peekIssue value
    IssueCommentCreate->>common.helper: Apply CSS class based on peekIssue
    IssueCommentCreate-->>User: Display styled component

Loading

Poem

🐇 In a world where comments grow,
A peek reveals what we should know.
With styles that shift like fluffy clouds,
Our UI dances, oh so proud!
Hopping through lines of code so fine,
Every change makes it truly shine! ✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 700f3ee and 3cf51b8.

Files selected for processing (1)

• web/core/components/issues/issue-detail/issue-activity/comments/comment-create.tsx (3 hunks)

Additional comments not posted (4)

web/core/components/issues/issue-detail/issue-activity/comments/comment-create.tsx (4)

10-10: Import of cn function looks good.

The import statement for the cn function is correctly added from common.helper.

---

13-13: Import of useIssueDetail hook looks good.

The import statement for the useIssueDetail hook is correctly added from store hooks.

---

31-31: Usage of peekIssue looks good.

The peekIssue variable is correctly used to conditionally apply CSS classes, enhancing the component's responsiveness.

---

63-65: Conditional class application looks good.

The cn function is used effectively to conditionally apply the -bottom-5 class based on the peekIssue state.