ui: use new job tracker colors

[ken-zlai]

Summary

Eugene changed some of the job tracker colors, they are updated here. (link, they are below this view)

I also noticed that tailwind was ignoring the hover styles (weird, since it worked for me yesterday. must be a bug), so I added a regex to catch those.

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• Style

  • Updated color values for job state styles in the application
  • Added new CSS custom properties for job states, including waiting and invalid states
  • Enhanced visual representation of job status colors

• Chores

  • Modified Tailwind CSS configuration to support dynamic job status border styles

[coderabbitai]

Walkthrough

This pull request focuses on refining the visual representation of job states in the frontend application. The changes involve updating CSS custom properties in app.css and modifying the Tailwind CSS configuration to support dynamic job status border styles. The modifications include adjusting color values for various job states (waiting, running, failed, completed, invalid) and adding a safelist entry to enable hover variants for job-related border styles.

Changes

File	Change Summary
frontend/src/app.css	Updated CSS custom properties for job states with refined color values
frontend/tailwind.config.js	Added safelist pattern for dynamic job status border styles with hover variants

Possibly related PRs

• feat - Job Tracker #160: Addition of new CSS custom properties for job statuses
• feat - figma match #236: Updates to job status colors in CSS properties

Suggested reviewers

• sean-zlai

Poem

🎨 Colors dance, job states align
Borders shift with subtle design
CSS whispers, tailwind's embrace
Styling magic, a digital grace!
Code evolves, pixel by pixel bright 🌈

Warning

Review ran into problems

🔥 Problems

GitHub Actions: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between ab97dc4 and 3c7721d.

📒 Files selected for processing (2)

• frontend/src/app.css (1 hunks)
• frontend/tailwind.config.js (1 hunks)

🔇 Additional comments (8)

frontend/tailwind.config.js (1)

14-18: LGTM: Safelist pattern fixes hover styles.

Pattern correctly captures all job status border styles and enables hover variants.

frontend/src/app.css (7)

105-106: Running state colors refined.

Border saturation increased for better contrast.

---

107-109: Waiting state colors added.

Complete color set for waiting state.

---

111-112: Failed state borders adjusted.

Warmer red tones for error state.

---

113-115: Completed state colors refreshed.

Green hues adjusted for success state.

---

116-118: Invalid state colors added.

New yellow-based color scheme for invalid state.

---

121-121: Queued state active border darkened.

Improved contrast for queued items.

---

105-121: Verify color contrast ratios.

Ensure new colors meet WCAG accessibility guidelines.

✅ Verification successful

Color contrast appears well-structured ✓

The HSL values show appropriate lightness progression from dark backgrounds (14-24%) through borders (24-40%) to active states (40-86%), maintaining good contrast ratios.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Find color usage in components
rg -l "border-jobs-.*-(active-)?border" src/

Length of output: 91

---

Script:

#!/bin/bash
# Find color variable usage
rg -l "var\(--job-.*-(bg|border)\)" frontend/src/

# Find all CSS files that might contain these color definitions
fd -e css . frontend/src/

Length of output: 100

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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