fix(notes): fix notes block spacing, additional logs for billing transfer route

[waleedlatif1]

Summary

• fix notes block spacing
• additional logs for billing transfer route

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Building	Preview	Comment	Nov 17, 2025 9:36pm

[greptile-apps]

Greptile Summary

• Fixed note block markdown spacing by replacing negative margins with proper mb-2, mt-3, and mb-1 classes
• Enhanced subscription transfer logging with info and error logs at key points in the organization creation and billing transfer flow

Confidence Score: 3/5

• This PR is safe to merge after fixing the TypeScript violations
• Score reflects the fact that while changes are functionally sound (UI spacing fix and improved logging), the note block introduces multiple any types that violate the project's strict TypeScript style guide
• Pay attention to note-block.tsx to fix TypeScript any type usage before merging

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/note-block/note-block.tsx	Fixed markdown spacing by removing negative margins and adding proper spacing, but introduced any types that violate style guide

Sequence Diagram

sequenceDiagram
    participant User
    participant UI as "Subscription Upgrade UI"
    participant Hook as "useSubscriptionUpgrade"
    participant API as "API Routes"
    participant Client as "Better Auth Client"
    participant Logger

    User->>UI: "Click upgrade to team plan"
    UI->>Hook: "handleUpgrade('team')"
    Hook->>Logger: "Creating organization for team plan upgrade"
    Hook->>API: "POST /api/organizations"
    API-->>Hook: "organizationId"
    Hook->>Logger: "Organization API response"
    Hook->>Client: "setActive(organizationId)"
    Hook->>Logger: "Set organization as active"
    Hook->>Logger: "Transferring personal subscription to organization"
    Hook->>API: "POST /api/users/me/subscription/{id}/transfer"
    alt Transfer successful
        API-->>Hook: "Success"
        Hook->>Logger: "Successfully transferred subscription to organization"
        Hook->>Client: "upgrade(params)"
        Client-->>Hook: "Redirect to payment"
        Hook->>Logger: "Subscription upgrade completed successfully"
        Hook-->>UI: "Success"
        UI-->>User: "Redirect to checkout"
    else Transfer failed
        API-->>Hook: "Error"
        Hook->>Logger: "Failed to transfer subscription to organization"
        Hook-->>UI: "Error"
        UI-->>User: "Show error message"
    end

Loading

[greptile-apps]

Additional Comments (1)

1. apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/note-block/note-block.tsx, line 38-113 (link)

   syntax: Using any type violates the style guide rule "No any types used". Define proper types for ReactMarkdown component props.

   Context Used: Context from dashboard - apps/sim/.cursorrules (source)

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile
React with 👍 or 👎 to share your feedback on this new summary format}