fix: add rounded corners to project and quick nav items

[Gahotx]

Description

Improve the rounded corners of the bottom left and right corners of the project and quick navigation modules

Before:

After:

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Style
  • Updated styling for WorkbenchProject and WorkbenchQuickNav components
  • Added rounded bottom corner classes for specific list items
  • Refined visual presentation of navigation and dashboard elements

[changeset-bot]

⚠️ No Changeset found

Latest commit: f01abca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/effects/common-ui/src/ui/dashboard/workbench/workbench-project.vue

Oops! Something went wrong! :(

ESLint: 9.17.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/node_modules/@vben/eslint-config/dist/index.mjs' imported from /eslint.config.mjs
at finalizeResolution (node:internal/modules/esm/resolve:257:11)
at moduleResolve (node:internal/modules/esm/resolve:914:10)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

Walkthrough

The pull request introduces consistent styling modifications to two Vue components in the workbench dashboard: workbench-project.vue and workbench-quick-nav.vue. The changes focus on adding conditional class bindings to specific div elements within v-for loops, specifically applying rounded-bl-xl and rounded-br-xl classes to items at specific indices. These modifications aim to enhance the visual presentation of the components by rounding the bottom corners of certain list items.

Changes

File	Change Summary
packages/effects/common-ui/src/ui/dashboard/workbench/workbench-project.vue	Added conditional class bindings for rounded-bl-xl and rounded-br-xl based on item indices
packages/effects/common-ui/src/ui/dashboard/workbench/workbench-quick-nav.vue	Added conditional class bindings for rounded-bl-xl and rounded-br-xl based on item indices

Possibly related PRs

• fix: form required style adjustment #4668: Modifies component template with similar conditional class bindings for styling based on item indices

Suggested reviewers

• vince292007
• anncwb

Poem

🐰 Rounded corners, soft and neat,
In workbench views, a styling treat
With classes that dance and sway
Bottom edges now smoothly play
A rabbit's design, precise and light! 🎨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 801c640 and 53bd542.

📒 Files selected for processing (2)

• packages/effects/common-ui/src/ui/dashboard/workbench/workbench-project.vue (1 hunks)
• packages/effects/common-ui/src/ui/dashboard/workbench/workbench-quick-nav.vue (1 hunks)

🔇 Additional comments (2)

packages/effects/common-ui/src/ui/dashboard/workbench/workbench-quick-nav.vue (1)

39-41: Validate index-based rounding logic.

These conditions apply extra rounding for specific items based on hardcoded indices:

• rounded-bl-xl → index === items.length - 3
• rounded-br-xl → index === items.length - 1

Verify that this logic behaves as intended for edge cases:

• When items has fewer than 3 elements, index === items.length - 3 may never be satisfied (no bottom-left corners get rounded).
• The last item is always rounded on the bottom-right corner.

It might be worth adding test items with lengths < 3 to ensure no visual anomalies occur or that you’re comfortable with the fallback appearance when the rounded-bl-xl condition fails for short arrays.

packages/effects/common-ui/src/ui/dashboard/workbench/workbench-project.vue (1)

40-41: Confirm consistency across both components.

The added conditions for bottom corners are the same as in workbench-quick-nav.vue. This ensures consistent design across both components. As a future consideration, you may want to centralize this logic if multiple components require row-based conditional corner rounding. Otherwise, the approach here looks straightforward and correct for the design goal.

---

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