Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Hotfix] Fix tabs vertical scroll issue #2369

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Conversation

Codebmk
Copy link
Member

@Codebmk Codebmk commented Jan 9, 2025

This pull request includes a small change to the Tabs component in the platform/src/common/components/Tabs/index.jsx file. The change removes the h-dvh class from the div element's className attribute.

image
image

Summary by CodeRabbit

  • Style
    • Updated styling for the Tabs component by removing a height-related class.

Copy link

coderabbitai bot commented Jan 9, 2025

📝 Walkthrough

Walkthrough

The pull request introduces a minor styling modification to the Tabs component in the platform's source code. Specifically, the h-dvh class has been removed from a div element's className, which potentially impacts the component's height and layout rendering. This change suggests a deliberate adjustment to the visual presentation of the Tabs component.

Changes

File Change Summary
platform/src/common/components/Tabs/index.jsx Removed h-dvh class from div's className, retaining other transition and width-related classes

Poem

A class removed, a height unbound 🏷️
Tabs dancing free, no constraints found
Pixels shift, layout takes flight
Styling whispers, soft and light
Code's subtle art, a gentle sway 🎨

Finishing Touches

  • 📝 Generate Docstrings

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
🪧 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 or @coderabbitai title 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
platform/src/common/components/Tabs/index.jsx (1)

72-72: Consider documenting the height behavior

Since this change affects the component's layout behavior, it would be helpful to add a brief comment explaining why we're not using viewport height constraints and how the height is now determined.

+  // Height is determined by content to prevent scroll issues
   className="relative w-full transition-all duration-300 ease-in-out"
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a88263d and c07b8bf.

📒 Files selected for processing (1)
  • platform/src/common/components/Tabs/index.jsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: test-analytics-platform-changes
🔇 Additional comments (2)
platform/src/common/components/Tabs/index.jsx (2)

72-72: LGTM! Removing h-dvh should fix the vertical scroll issue.

The removal of the dynamic viewport height constraint allows the container to naturally size based on its content, which should resolve the scrolling problems while maintaining the component's responsive behavior.


Line range hint 74-81: Verify the impact on fixed positioning scenarios

Since we removed the viewport height constraint, please verify that this change doesn't affect the component's behavior when positionFixed={true} is used, especially in layouts where the tabs need to stick to the viewport.

Run this script to find usage examples:

✅ Verification successful

Fixed positioning behavior remains intact and reliable

The removal of the viewport height constraint doesn't affect the fixed positioning functionality. The component maintains proper spacing and layout through explicit height classes (h-14 for the tabs container and h-8 for the spacer), while the fixed positioning is correctly handled by the fixed class when positionFixed={true} is used.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for Tabs component usage with positionFixed prop
ast-grep --pattern 'Tabs $$$positionFixed={true}$$$'

# Alternatively, search for any Tabs usage
rg -l "import.*Tabs.*from.*common/components/Tabs" | xargs rg "<Tabs.*positionFixed"

Length of output: 141


Script:

#!/bin/bash
# Find all possible Tabs imports and usages with broader patterns
rg -i "import.*tabs.*from" --type jsx --type tsx

# Find any Tabs component usage
rg -i "<tabs.*>" --type jsx --type tsx

# Look for position-fixed or positionFixed prop specifically
rg -i "position-?fixed" --type jsx --type tsx

# Examine the Tabs component implementation
cat platform/src/common/components/Tabs/index.jsx

Length of output: 2997

Copy link
Contributor

github-actions bot commented Jan 9, 2025

New next-platform changes available for preview here

@Baalmart Baalmart merged commit f5c8b3d into staging Jan 9, 2025
30 of 31 checks passed
@Baalmart Baalmart deleted the hotfix-analaytics-tabs branch January 9, 2025 19:56
@Baalmart Baalmart mentioned this pull request Jan 9, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants