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

fix(20649): Always show numbers in Bivariate hex popup #964

Merged
merged 2 commits into from
Jan 22, 2025

Conversation

albaranau
Copy link
Contributor

@albaranau albaranau commented Jan 22, 2025

https://kontur.fibery.io/Tasks/Task/Show-numbers-in-bivariate-popup-by-default-20649

image

Summary by CodeRabbit

  • Refactor
    • Simplified rendering logic for map hex tooltips.
    • Removed feature flag dependency for displaying values in map tooltips.
    • Made values a required property in map hex tooltip component, ensuring consistent value display.

@albaranau albaranau requested a review from a team January 22, 2025 10:22
Copy link
Contributor

coderabbitai bot commented Jan 22, 2025

Walkthrough

The changes involve simplifying the rendering logic in the BivariateRenderer by removing a feature flag-based condition for displaying values in a map tooltip. The modification eliminates the conditional check that previously controlled the visibility of x and y values, ensuring that the values are always passed to the tooltip component regardless of previous feature flag settings. Additionally, the MapHexTooltip component now requires the values prop, enforcing stricter usage.

Changes

File Change Summary
src/core/logical_layers/renderers/BivariateRenderer/BivariateRenderer.tsx Removed featureFlags variable and unconditional value passing to MapHexTooltip.
src/components/MapHexTooltip/MapHexTooltip.tsx Updated MapHexTooltipProps to require values and removed conditional rendering for values.

Poem

🐰 Flags fall away, logic grows clear
Values now flow without a fear
Tooltips shine bright, no conditions bind
Simple code speaks with a rabbit's mind!
Rendering pure, no flags to hide 🌈


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

Language To Recheck Fuzzy Untranslated Total
ar 3 24 101 128
de 2 24 101 127
es 3 24 101 128
id 2 24 101 127
ko 3 24 101 128
uk 0 7 8 15

Copy link

github-actions bot commented Jan 22, 2025

Bundle size diff

Old size New size Diff
5.16 MB 5.16 MB -78 B (-0.00%)

Copy link

Preview environments for this PR:

These previews are automatically updated with each commit.

Note: After a new deployment, it may take a few minutes for the changes to propagate and for caches to update. During this time, you might experience temporary loading issues or see an older version of the app. If the app fails to load, please wait a few minutes and try again.

Copy link

codecov bot commented Jan 22, 2025

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 10.04%. Comparing base (d469784) to head (4b67a60).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/components/MapHexTooltip/MapHexTooltip.tsx 0.00% 3 Missing ⚠️
.../renderers/BivariateRenderer/BivariateRenderer.tsx 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #964   +/-   ##
=======================================
  Coverage   10.04%   10.04%           
=======================================
  Files         668      668           
  Lines       29398    29395    -3     
  Branches     1235     1235           
=======================================
  Hits         2954     2954           
+ Misses      25915    25912    -3     
  Partials      529      529           
Components Coverage Δ
UI Components 0.26% <0.00%> (+<0.01%) ⬆️
Core Logic 17.81% <0.00%> (+<0.01%) ⬆️
Features 1.13% <ø> (ø)
Utilities 45.77% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

codecov bot commented Jan 22, 2025

Bundle Report

Changes will decrease total bundle size by 78 bytes (-0.0%) ⬇️. This is within the configured threshold ✅

Detailed changes
Bundle name Size Change
konturio/disaster-ninja-fe-esm 5.41MB 78 bytes (-0.0%) ⬇️

Copy link
Contributor

@Natallia-Harshunova Natallia-Harshunova left a comment

Choose a reason for hiding this comment

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

If you 100% sure that values always should be presented in such tooltip, you can also remove optional from props definition of MapHexTooltipProps

Copy link
Contributor

@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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9e450db and 4b67a60.

📒 Files selected for processing (1)
  • src/components/MapHexTooltip/MapHexTooltip.tsx (2 hunks)
🔇 Additional comments (1)
src/components/MapHexTooltip/MapHexTooltip.tsx (1)

33-33: Breaking change: values prop is now required.

Making the values prop required is a breaking change that will affect all consumers of this component. While this aligns with the PR objective to always show numbers, we should verify that all usage sites provide this prop.

Let's verify all component usages:

✅ Verification successful

Making values prop required is safe

The only usage of MapHexTooltip in the codebase (in BivariateRenderer.tsx) already provides the required values prop with both x and y values. This change aligns with the existing implementation and won't cause any breaking changes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Find all files that import or use MapHexTooltip
rg -l "MapHexTooltip"

# Search for MapHexTooltip usage patterns
ast-grep --pattern 'MapHexTooltip $$$'

Length of output: 183


Script:

#!/bin/bash
# Look for MapHexTooltip JSX usage with context
rg -U "MapHexTooltip.*?>" -A 5 -B 5 src/core/logical_layers/renderers/BivariateRenderer/BivariateRenderer.tsx

# Alternative search using ast-grep for JSX element
ast-grep --pattern '<MapHexTooltip $$$>'

Length of output: 154


Script:

#!/bin/bash
# Check import statement
rg "import.*MapHexTooltip" src/core/logical_layers/renderers/BivariateRenderer/BivariateRenderer.tsx

# Get more context around any MapHexTooltip mention
rg -A 10 -B 10 "MapHexTooltip" src/core/logical_layers/renderers/BivariateRenderer/BivariateRenderer.tsx

# Try to find any component props spread
rg -A 5 -B 5 "{\s*\.\.\..*}" src/core/logical_layers/renderers/BivariateRenderer/BivariateRenderer.tsx

Length of output: 1971

@albaranau albaranau merged commit 0e63b26 into main Jan 22, 2025
16 of 22 checks passed
@albaranau albaranau deleted the 20649-show-numbers-in-bivariate-popup-by-default branch January 22, 2025 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants