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: dashboard panel light theme #4556

Merged
merged 3 commits into from
Feb 15, 2024
Merged

Conversation

vikrantgupta25
Copy link
Collaborator

@vikrantgupta25 vikrantgupta25 commented Feb 15, 2024

Summary

  • added light theme for dashboard side panel
  • handle page crash for logs pipeline stimulated logs

Related Issues / PR's

Screenshots

Screen.Recording.2024-02-15.at.3.46.29.PM.mov

Affected Areas and Manually Tested Areas

Summary by CodeRabbit

Summary by CodeRabbit

  • Style
    • Introduced light mode styling for the dropdown menu, including hover effects for enhanced user interaction.

Copy link

coderabbitai bot commented Feb 15, 2024

Walkthrough

This update introduces a dedicated light mode for the dropdown menu in the application's front end. The enhancement focuses on visual modifications such as border styling, background color adjustments, and box-shadow effects. Additionally, it incorporates interactive hover effects tailored to different classes of menu items, enriching the user interface with a more dynamic and visually appealing experience.

Changes

File Path Change Summary
frontend/src/styles.scss Added styles for light mode in dropdown menu, including border, background, box-shadow, and hover effects for items.
frontend/src/lib/logs/flatLogData.ts Imported defaultTo from 'lodash-es' and updated logic in FlatLogData function to use defaultTo when iterating over object keys.

🐇
In the realm of code, where the bits gently hop,
A rabbit worked hard, at the screen did not stop.
With a flick and a click, a new style was born,
Light mode in dropdowns, no more visually torn.
Borders and shadows, now gracefully stand,
Hover and glow, at the coder's command.
🌟🎉

Related issues

  • [EPIC] Dashboard improvements #3573: The changes in frontend/src/lib/logs/flatLogData.ts align with the objective of implementing improvements related to logs, which is in line with the enhancements mentioned in this issue.

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>.
    • Generate unit-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

@github-actions github-actions bot added the bug Something isn't working label Feb 15, 2024
Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 4e75479 and 515ad3a.
Files selected for processing (1)
  • frontend/src/styles.scss (1 hunks)
Additional comments: 1
frontend/src/styles.scss (1)
  • 228-244: The new .lightMode styles for .ant-dropdown-menu and .ant-dropdown-menu-item correctly implement the intended visual enhancements for the light theme. However, ensure that the variable --bg-vanilla-300 and --bg-vanilla-100 are defined in @signozhq/design-tokens/dist/style.css or elsewhere in the project to avoid potential issues with undefined variables.
Verification successful

The search results confirm that the CSS variables --bg-vanilla-300 and --bg-vanilla-100 are indeed used throughout the project in various SCSS files, including the specific instances within frontend/src/styles.scss as mentioned in the review comment. This indicates that these variables are defined and utilized across the project, supporting the review comment's suggestion to ensure these variables are defined to avoid potential issues with undefined variables.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify if the variables are defined in the project
rg --type scss 'var\(--bg-vanilla-300\)|var\(--bg-vanilla-100\)'

Length of output: 95



Script:

#!/bin/bash
# Corrected command to search for the variables in SCSS files
rg 'var\(--bg-vanilla-300\)|var\(--bg-vanilla-100\)' -g '*.scss'

Length of output: 11458

Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

1 similar comment
Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

frontend/src/styles.scss Outdated Show resolved Hide resolved
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.

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 515ad3a and 46576a3.
Files selected for processing (2)
  • frontend/src/lib/logs/flatLogData.ts (2 hunks)
  • frontend/src/styles.scss (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • frontend/src/styles.scss
Additional comments: 1
frontend/src/lib/logs/flatLogData.ts (1)
  • 1-1: The import of defaultTo from 'lodash-es' is correctly added to handle potential null or undefined values gracefully.

frontend/src/lib/logs/flatLogData.ts Show resolved Hide resolved
Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

@vikrantgupta25 vikrantgupta25 merged commit 548c531 into develop Feb 15, 2024
11 of 12 checks passed
@srikanthccv srikanthccv deleted the fix-dashboard-colors branch April 11, 2024 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants