Added the Attempt span error back (and properties)

[matt-aitken]

I accidentally removed the Attempt span error block when I created the separate component to render attempts… this brings it back

Summary by CodeRabbit

• New Features
  • Enhanced span detail display now conditionally shows event information and properties when available.
• Style
  • Adjusted component spacing to improve vertical layout.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a350f7d

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.

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 pull request updates the span detail rendering logic in the SpanEntity function. The changes include updating the margin class for the WarmStartCombo component from "mt-3" to "my-3", and adding two conditional renderings. One displays a SpanEvents component when the span.events array is non-empty, and the other renders a CodeBlock component if span.properties is defined. No public entity declarations were modified.

Changes

File (simplified)	Summary of Changes
apps/webapp/app/routes/.../route.tsx	Updated WarmStartCombo margin class from "mt-3" to "my-3"; added conditional rendering for SpanEvents and CodeBlock based on span data.

Sequence Diagram(s)

sequenceDiagram
    participant SE as SpanEntity
    participant WSC as WarmStartCombo
    participant SEvt as SpanEvents
    participant CB as CodeBlock

    SE->>WSC: Render with class "my-3"
    alt If span.events exists
        SE->>SEvt: Render SpanEvents
    end
    alt If span.properties exists
        SE->>CB: Render CodeBlock
    end

Loading

Poem

I hopped through lines of code today,
Adjusting classes in a smart new way.
With events and properties shining bright,
I’ve added details with all my might.
Coding fields bloom under my gentle paw,
A rabbit celebration—hip-hip, hurrah! 🐇

---

📜 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 3cbbece and a350f7d.

📒 Files selected for processing (1)

• apps/webapp/app/routes/resources.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs.$runParam.spans.$spanParam/route.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: units / 🧪 Unit Tests
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

apps/webapp/app/routes/resources.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs.$runParam.spans.$spanParam/route.tsx (2)

962-963: Margin adjustment improves spacing around the WarmStartCombo component.

The change from "mt-3" (margin-top) to "my-3" (margin-top and margin-bottom) creates more consistent spacing around the component, which is particularly important now that additional content may appear below it.

---

965-973: Successfully restored the Attempt span error block.

The added conditional rendering blocks for span events and properties match the pattern used in the normal span case (lines 919-928), correctly restoring the functionality that was inadvertently removed. This implementation ensures:

1. Events are only displayed when the span has events
2. Properties are displayed in a CodeBlock with appropriate formatting when defined

This change aligns perfectly with the PR objective of restoring the Attempt span error block.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.