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:Modify panel shadow color #943

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

xuanlid
Copy link
Contributor

@xuanlid xuanlid commented Dec 18, 2024

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

Background and solution

增加base变量,更改面板阴影颜色
image
image
image
image
image

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • New Features

    • Introduced a new tiny-search component for enhanced search functionality.
    • Added an import button for schema management.
  • Improvements

    • Enhanced file handling and loading indicators in the internationalization resource panel.
    • Improved error handling for schema parsing and validation processes.
    • Updated styling across components to utilize CSS variables for better maintainability.
  • Bug Fixes

    • Addressed validation checks for variable and store creation to prevent errors.

Copy link
Contributor

coderabbitai bot commented Dec 18, 2024

Walkthrough

This pull request introduces consistent styling improvements across multiple Vue components and the base theme. The primary change involves introducing a new CSS variable --te-base-box-shadow-rgba-3 in the base theme, which is then used to standardize box shadow styling in various plugin components like PluginSetting.vue, Main.vue for different plugins (i18n, schema, script, state). The modifications maintain existing component functionality while enhancing styling flexibility and maintainability.

Changes

File Change Summary
packages/common/component/PluginSetting.vue Updated .plugin-setting class box shadow to use CSS variable
packages/plugins/i18n/src/Main.vue Enhanced template structure, added new component properties, updated styling with CSS variable
packages/plugins/schema/src/Main.vue Improved error handling, added schema import button, updated box shadow styling
packages/plugins/script/src/Main.vue Modified box shadow styling, maintained core editor initialization logic
packages/plugins/state/src/Main.vue Added box shadow, introduced new search component, enhanced validation methods
packages/theme/base/src/base.less Added new CSS variable --te-base-box-shadow-rgba-3: rgba(0, 0, 0, 0.1)

Possibly related PRs

Suggested labels

refactor-main, enhancement

Suggested reviewers

  • hexqi
  • chilingling

Poem

🐰 Shadows soft as rabbit's fur,
CSS variables now confer
Styling magic, clean and bright
Components dance with pure delight!
A theme that hops from gray to clear 🎨


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.

@github-actions github-actions bot added bug Something isn't working refactor-main refactor/develop branch feature labels Dec 18, 2024
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: 0

🧹 Nitpick comments (7)
packages/plugins/script/src/Main.vue (2)

105-105: Consider reducing shadow size for subtlety

The 6px offset for the box shadow appears quite prominent for a panel shadow. Consider reducing it to 3px for a more subtle effect while maintaining the visual hierarchy.

-  box-shadow: 6px 0px 3px 0px var(--te-base-box-shadow-rgba-3);
+  box-shadow: 3px 0px 3px 0px var(--te-base-box-shadow-rgba-3);

108-108: Review z-index value for potential stacking context issues

The z-index of 999 is quite high and might cause issues with other overlapping elements. Consider using a lower value or implementing a z-index management system.

Consider implementing a z-index scale in your theme variables:

// In your theme file
:root {
  --z-index-panel: 100;
  --z-index-modal: 200;
  // ... other z-index values
}
packages/common/component/PluginSetting.vue (1)

137-139: LGTM with a minor suggestion

The implementation of conditional shadow and use of CSS variable is clean and well-structured. For consistency with other components, consider the same shadow size reduction suggested earlier.

-    box-shadow: 6px 0px 3px 0px var(--te-base-box-shadow-rgba-3);
+    box-shadow: 3px 0px 3px 0px var(--te-base-box-shadow-rgba-3);
packages/plugins/schema/src/Main.vue (3)

151-151: Maintain consistent shadow properties across components

For consistency with other panel shadows, consider reducing the shadow offset.

-  box-shadow: 6px 0px 3px 0px var(--te-base-box-shadow-rgba-3);
+  box-shadow: 3px 0px 3px 0px var(--te-base-box-shadow-rgba-3);

152-152: Standardize z-index values across panels

The z-index value (1000) differs from the script panel (999). Consider standardizing these values using CSS variables.

Consider implementing a z-index management system as suggested earlier.


Line range hint 11-17: Remove hidden popover instead of using v-show="false"

Rather than hiding the popover with v-show="false", consider removing it entirely until it's needed.

-        <tiny-popover v-show="false" placement="bottom" trigger="hover" append-to-body content="导入 Schema">
-          <template #reference>
-            <span class="icon-wrap">
-              <icon-download-link></icon-download-link>
-            </span>
-          </template>
-        </tiny-popover>
packages/theme/base/src/base.less (1)

242-242: LGTM! Consider adding a comment to document the variable's purpose.

The new box shadow variable follows the established naming pattern and uses an appropriate value for subtle shadows.

Add a comment above the variable to document its intended use case:

+  // Subtle box shadow for panel overlays
   --te-base-box-shadow-rgba-3: rgba(0, 0, 0, 0.1);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eb76a70 and ef90267.

📒 Files selected for processing (6)
  • packages/common/component/PluginSetting.vue (1 hunks)
  • packages/plugins/i18n/src/Main.vue (1 hunks)
  • packages/plugins/schema/src/Main.vue (1 hunks)
  • packages/plugins/script/src/Main.vue (1 hunks)
  • packages/plugins/state/src/Main.vue (1 hunks)
  • packages/theme/base/src/base.less (1 hunks)
🔇 Additional comments (2)
packages/plugins/state/src/Main.vue (1)

455-455: LGTM! Consistent use of the new shadow variable.

The box shadow implementation helps create visual hierarchy and follows the new design system variable.

packages/plugins/i18n/src/Main.vue (1)

436-436: LGTM! Consistent shadow styling across plugin panels.

The implementation maintains visual consistency with other plugin panels by using the shared shadow variable.

@hexqi hexqi merged commit a14a508 into opentiny:refactor/develop Jan 7, 2025
8 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jan 16, 2025
14 tasks
@xuanlid xuanlid deleted the develop-lx-panel branch January 24, 2025 09:04
@xuanlid xuanlid restored the develop-lx-panel branch January 24, 2025 09:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working refactor-main refactor/develop branch feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants