[WEB-2209] chore: made cursor update on created_by in issue properties pane in issue detail, and issue peek overview

[gurusainath]

Summary:

• Made cursor update from cursor-default to cursor-not-allowed on created_by in the issue properties pane in issue detail, and issue peek overview

Plane Issue:

[WEB-2209]

Summary by CodeRabbit

• User Interface Enhancements
  • Updated styling for non-interactive elements in the sidebar, improving visual cues for user interaction.
  • Ensured full-width display for user information in the sidebar, enhancing layout consistency.
  • Altered cursor styling in the Peek Overview component to indicate non-interactive areas, improving user experience.

[coderabbitai]

Walkthrough

The recent changes enhance the user interface of the IssueDetailsSidebar and PeekOverviewProperties components by updating the cursor styles to indicate non-interactivity. This change improves user experience by visually signaling that certain elements are not interactive, while also ensuring layout consistency with the addition of full-width styling. Overall, these modifications contribute to a clearer and more intuitive interface.

Changes

Files	Change Summary
web/core/components/issues/.../sidebar.tsx	Changed cursor style from cursor-default to cursor-not-allowed for non-interactive elements; set width to w-full for better layout consistency.
web/core/components/issues/.../properties.tsx	Altered cursor style from cursor-default to cursor-not-allowed to indicate non-interactivity, enhancing user experience without affecting component logic.

Poem

🐇 In the sidebar where users roam,
Cursors now signal, "This space is home!"
With widths that stretch, a layout so neat,
Interactive areas, no longer a feat.
Click not in vain, for here’s the delight,
A clear path to follow, from morning to night! 🌟

---

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 e805c49 and 8f46f91.

Files selected for processing (2)

• web/core/components/issues/issue-detail/sidebar.tsx (1 hunks)
• web/core/components/issues/peek-overview/properties.tsx (1 hunks)

Additional comments not posted (2)

web/core/components/issues/peek-overview/properties.tsx (1)

136-136: Cursor style change approved.

The update to cursor-not-allowed accurately reflects the non-interactive nature of the "created_by" element, enhancing user experience.

web/core/components/issues/issue-detail/sidebar.tsx (1)

134-134: Cursor style and layout changes approved.

The update to cursor-not-allowed and setting the width to w-full enhance the user experience by signaling non-interactivity and ensuring layout consistency.