[PWA-23] chore: disable hover effect pwa

[anmolsinghbhatia]

Changes:

This PR includes following changes:

• Removed the hover effect from the app sidebar, issue layout, and modals in the PWA, allowing users to interact with a single tap instead of two.
• Fixed the Calendar PWA layout and corrected the issue with redirection.
• Refactored the rendering logic for the issue detail sidebar.

Reference:

[PWA-23]

Summary by CodeRabbit

• New Features

  • Enhanced responsiveness of the user interface by conditionally rendering components based on mobile device detection.
  • Improved styling logic for various components, ensuring a cleaner and more intuitive experience on mobile devices.

• Bug Fixes

  • Adjusted hover effects and interactions for mobile users to prevent unnecessary clutter and improve usability.

• Chores

  • Streamlined class name management across components for better maintainability and readability.

[coderabbitai[bot]]

Walkthrough

The pull request introduces significant modifications across various components to enhance responsiveness and styling based on the isMobile state. Changes include the refactoring of class name management using the cn helper function, conditional rendering of components based on platform detection, and the removal of mobile-specific layouts. These alterations aim to streamline the user interface and improve the overall adaptability of the application across different devices.

Changes

Files	Change Summary
web/core/components/core/modals/existing-issues-list-modal.tsx	Enhanced styling logic with cn function for class names; refactored button class management based on isMobile.
web/core/components/issues/issue-detail/root.tsx	Introduced usePlatformOS hook for conditional rendering of IssueDetailsSidebar based on mobile platform detection.
web/core/components/issues/issue-layouts/calendar/calendar.tsx	Removed mobile view rendering logic, eliminating props related to mobile interactivity in CalendarChart.
web/core/components/issues/issue-layouts/calendar/issue-block.tsx	Updated button disabled logic to only consider issue.tempId, allowing mobile interaction; adjusted class conditions based on isMobile.
web/core/components/issues/issue-layouts/list/block.tsx	Streamlined class names and hover effects based on isMobile, improving responsiveness and visual feedback.
web/core/components/issues/parent-issues-list-modal.tsx	Adjusted z-index and class names for list items based on isMobile, enhancing mobile responsiveness.
web/core/components/workspace/sidebar/favorites/favorites-menu.tsx	Modified class names for button and span elements to enhance hover behavior based on isMobile.
web/core/components/workspace/sidebar/projects-list-item.tsx	Simplified class name logic for main div and button, improving readability and conditional rendering based on isMobile.
web/core/components/workspace/sidebar/projects-list.tsx	Added usePlatformOS hook for conditional rendering and class name adjustments based on isMobile.
web/core/components/workspace/sidebar/workspace-menu.tsx	Enhanced responsiveness by conditionally applying class names and hover effects based on isMobile.

Possibly related PRs

• #5533: Changes in ModuleCardItem and ModuleListItemAction involve enhancements to user interaction and conditional rendering, relating to the improvements in responsiveness.
• #5549: Modifications in AppSidebar focus on maintaining the sidebar's collapse state based on window size, aligning with the PR's emphasis on UI responsiveness.

Poem

🐰 In the meadow where the bunnies play,
Changes hop in, brightening the day.
With styles that dance and buttons that gleam,
Mobile or not, we’re living the dream!
Responsive and sleek, our UI's a delight,
Hopping along, everything feels just right! 🌼

[!TIP]

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

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 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 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.