Skip to content

Adds a tooltip to the Status header showing deployment status descrip… #1554

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

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

samejr
Copy link
Member

@samejr samejr commented Dec 12, 2024

A tooltip now explains the statuses of the build process.

PENDING and CANCELED are available in the data but I omitted them from the UI as they're not being used.

CleanShot 2024-12-12 at 16 46 34@2x

Summary by CodeRabbit

  • New Features

    • Enhanced deployment status display with detailed tooltips in the deployments table.
    • Introduced contextual descriptions for each deployment status.
  • Bug Fixes

    • Improved clarity of deployment statuses in the user interface.
  • Documentation

    • Updated status header to provide a more interactive experience for users.

Copy link

changeset-bot bot commented Dec 12, 2024

⚠️ No Changeset found

Latest commit: 63cd646

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

Copy link
Contributor

coderabbitai bot commented Dec 12, 2024

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.

apps/webapp/app/components/runs/v3/DeploymentStatus.tsx

Oops! Something went wrong! :(

ESLint: 8.45.0

ESLint couldn't find the config "custom" to extend from. Please check that the name of the config is correct.

The config "custom" was referenced from the config file in "/.eslintrc.js".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

The changes introduce a new constant deploymentStatuses and a function deploymentStatusDescription in the DeploymentStatus.tsx file, which provide updated deployment status information for the UI. The route.tsx file is modified to integrate these new features, enhancing the deployment status display in the deployments table with dynamic tooltips that show detailed descriptions of each status. The overall functionality remains intact, with improved presentation for user clarity.

Changes

File Change Summary
apps/webapp/app/components/runs/v3/DeploymentStatus.tsx Added constant deploymentStatuses and function deploymentStatusDescription.
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.v3.$projectParam.deployments/route.tsx Updated imports to include deploymentStatuses and deploymentStatusDescription, modified table header for dynamic status display.

Possibly related PRs

Suggested reviewers

  • matt-aitken

Poem

In the garden where statuses bloom,
Deployment tales dispel the gloom.
With descriptions now clear and bright,
Each status shines, a guiding light.
Hops of joy for updates new,
In our app, the changes grew! 🐇✨


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. (Experiment)
  • @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.

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

🧹 Outside diff range and nitpick comments (3)
apps/webapp/app/components/runs/v3/DeploymentStatus.tsx (2)

122-129: LGTM! Consider type safety improvements.

The deploymentStatuses constant correctly excludes unused statuses with a clear explanatory comment.

Consider using const assertion for better type safety:

-export const deploymentStatuses: WorkerDeploymentStatus[] = [
+export const deploymentStatuses = [
   "BUILDING",
   "DEPLOYING",
   "DEPLOYED",
   "FAILED",
   "TIMED_OUT",
-];
+] as const;

131-151: LGTM! Consider adding JSDoc documentation.

The deploymentStatusDescription function provides clear and user-friendly descriptions for all statuses.

Consider adding JSDoc documentation to improve IDE support:

+/**
+ * Returns a user-friendly description for each deployment status
+ * @param status - The deployment status to describe
+ * @returns A string description of the status
+ */
export function deploymentStatusDescription(status: WorkerDeploymentStatus): string {
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.v3.$projectParam.deployments/route.tsx (1)

127-150: Consider extracting tooltip content to a separate component.

While the implementation is solid, the tooltip content could be extracted to improve maintainability.

Consider creating a separate component:

+function StatusTooltipContent() {
+  return (
+    <div className="flex flex-col divide-y divide-grid-dimmed">
+      {deploymentStatuses.map((status) => (
+        <div
+          key={status}
+          className="grid grid-cols-[8rem_1fr] gap-x-2 py-2 first:pt-1 last:pb-1"
+        >
+          <div className="mb-0.5 flex items-center gap-1.5 whitespace-nowrap">
+            <DeploymentStatus status={status} isBuilt={false} />
+          </div>
+          <Paragraph
+            variant="extra-small"
+            className="!text-wrap text-text-dimmed"
+          >
+            {deploymentStatusDescription(status)}
+          </Paragraph>
+        </div>
+      ))}
+    </div>
+  );
+}

 <TableHeaderCell
-  tooltip={
-    <div className="flex flex-col divide-y divide-grid-dimmed">
-      {deploymentStatuses.map((status) => (
-        <div
-          key={status}
-          className="grid grid-cols-[8rem_1fr] gap-x-2 py-2 first:pt-1 last:pb-1"
-        >
-          <div className="mb-0.5 flex items-center gap-1.5 whitespace-nowrap">
-            <DeploymentStatus status={status} isBuilt={false} />
-          </div>
-          <Paragraph
-            variant="extra-small"
-            className="!text-wrap text-text-dimmed"
-          >
-            {deploymentStatusDescription(status)}
-          </Paragraph>
-        </div>
-      ))}
-    </div>
-  }
+  tooltip={<StatusTooltipContent />}
+  aria-label="Deployment status explanations"
 >
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1c631a1 and 63cd646.

📒 Files selected for processing (2)
  • apps/webapp/app/components/runs/v3/DeploymentStatus.tsx (1 hunks)
  • apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.v3.$projectParam.deployments/route.tsx (2 hunks)
🔇 Additional comments (1)
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.v3.$projectParam.deployments/route.tsx (1)

38-42: LGTM! Imports are well organized.

The new imports are logically grouped and correctly imported from the DeploymentStatus component.

Copy link

pkg-pr-new bot commented Dec 12, 2024

@trigger.dev/build

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1554

@trigger.dev/core

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/core@1554

@trigger.dev/react-hooks

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/react-hooks@1554

@trigger.dev/rsc

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/rsc@1554

trigger.dev

npm i https://pkg.pr.new/triggerdotdev/trigger.dev@1554

@trigger.dev/sdk

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1554

commit: 63cd646

@matt-aitken matt-aitken merged commit 7f2365f into main Dec 13, 2024
9 checks passed
@matt-aitken matt-aitken deleted the deployment-page-status-info branch December 13, 2024 11:11
@coderabbitai coderabbitai bot mentioned this pull request Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants