fix: show expired token label

[YounixM]

Summary by CodeRabbit

• New Features
  • Added functionality to check if an API key is expired using dayjs.
  • UI now visually indicates expired API keys.

[github-actions]

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

[coderabbitai]

Walkthrough

The update introduces a feature in the frontend that allows users to visually identify expired API keys. It leverages dayjs to compare the current date with the expiry timestamp of each API key, marking those that have expired. This enhancement aids in better management and awareness of API key validity directly from the user interface.

Changes

File Path	Change Summary
frontend/src/container/APIKeys/APIKeys.tsx	Added functionality to check for expired API keys using dayjs and updated UI to indicate expiration.

🐇✨
In the land of code and keys,
A rabbit hopped with ease.
"Expired or not?" it pondered deep,
With dayjs, no key shall sleep.
🌟🔑

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

[github-actions]

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

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ecd5ce9 and f06ebdf.

Files selected for processing (1)

• frontend/src/container/APIKeys/APIKeys.tsx (5 hunks)

Additional comments: 2

frontend/src/container/APIKeys/APIKeys.tsx (2)

• 324-328: The implementation of isExpiredToken correctly uses dayjs to compare the expiry timestamp of an API key with the current time. This is a clean and efficient way to determine if a token has expired.
• 29-29: The addition of dayjs as an import is correctly placed and necessary for the functionality being implemented. Ensure that dayjs is included in the project's dependencies in package.json to avoid any runtime errors.

Verification successful

---

The verification process has successfully identified that dayjs is included in the project's package.json dependencies, as indicated by the line "dayjs": "^1.10.7",. This confirms that the addition of dayjs as an import in the APIKeys.tsx file is supported by the project's dependencies, aligning with the initial review comment's guidance to ensure dayjs is included to avoid any runtime errors.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Check if dayjs is added to package.json dependencies
grep '"dayjs":' package.json

Length of output: 76

---

---

Script:

#!/bin/bash
# Locate package.json and check if dayjs is added to dependencies
fd package.json --exec grep '"dayjs":' {}

Length of output: 67

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between f06ebdf and aadf769.

Files selected for processing (1)

• frontend/src/container/APIKeys/APIKeys.tsx (5 hunks)

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

• frontend/src/container/APIKeys/APIKeys.tsx

[github-actions]

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