style: mod tag input and tag color

[yangxiaolang]

Summary by CodeRabbit

• Style
  • Updated tag background and border colors for improved consistency and contrast.
  • Adjusted disabled and read-only tag states to streamline background color handling.
  • Refined the appearance of info tags by using a slightly darker shade.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d03701f

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]

Walkthrough

The changes update SCSS styles for tag components by adjusting background and border colors. Specific color shades are modified or removed for certain states and variants, including .aui-tag, .aui-tag--info, and their disabled or readonly states. No changes to public APIs or exported entities are present.

Changes

File(s)	Change Summary
src/input/tags-input/mixin.scss	Updated .aui-tag to use background-color: use-rgb(n-7); removed background color for .isDisabled .aui-tag.
src/select/multi-select/multi-select.component.scss	Removed .aui-tag--info background color and .isReadonly .aui-tag background color.
src/tag/tag.component.scss	Changed .aui-tag--info background and .aui-tag--info.hasBorder background color from use-rgb(n-7) to use-rgb(n-8); border color unchanged.

Poem

A tag of color, shade anew,
From n-7 to n-8 we flew.
Info tags now slightly deep,
While disabled tags no color keep.
Styles refined, so neat and bright—
The rabbit hops with CSS delight!
🐇🎨

---

📜 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 d03701f and 83120f3.

📒 Files selected for processing (1)

• src/tag/tag.component.scss (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/tag/tag.component.scss

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Redirect rules - aui
• GitHub Check: Header rules - aui
• GitHub Check: Pages changed - aui
• GitHub Check: Unit Test
• GitHub Check: Release Beta

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/tag/tag.component.scss (1)

138-141: Redundant background override inside .hasBorder block

Inside .hasBorder you first set

border-color: use-rgb(n-8);

then immediately overwrite the background with use-rgb(button-bg), meaning the earlier background-color: use-rgb(n-8) (at line 136) is ignored whenever .hasBorder is present.

Consider dropping the first background declaration to avoid dead CSS:

-    background-color: use-rgb(n-8);

Keeps the file leaner and avoids future confusion.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f255c12 and d03701f.

📒 Files selected for processing (3)

• src/input/tags-input/mixin.scss (1 hunks)
• src/select/multi-select/multi-select.component.scss (0 hunks)
• src/tag/tag.component.scss (1 hunks)

💤 Files with no reviewable changes (1)

• src/select/multi-select/multi-select.component.scss

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Redirect rules - aui
• GitHub Check: Header rules - aui
• GitHub Check: Unit Test
• GitHub Check: Release Beta
• GitHub Check: Pages changed - aui

🔇 Additional comments (2)

src/input/tags-input/mixin.scss (1)

18-21: Confirm new default bg color provides sufficient contrast in light & dark themes

use-rgb(n-7) is now the always-on background for every .aui-tag inside the input.
Please double-check:

1. Contrast ratio against the default text colour returned by use-text-color(main) meets WCAG AA.
2. No unintended clash with .aui-tag--info, which was darkened to n-8 in tag.component.scss.

If either fails, consider a slightly lighter token (e.g. n-6) or reverting to a theme-aware mixin.

src/tag/tag.component.scss (1)

134-137: Shade shift to n-8 might render text (n-2) too low-contrast

Moving the info tag’s background from n-7 ➜ n-8 darkens it; the foreground text colour is still n-2.
Run a quick contrast audit to ensure the new pair still passes 4.5:1 for normal text sizes.

If it fails, either revert to n-7 or bump the text to a lighter token (e.g. n-1).