Skip to content

escape $ in stripe-projects.mdx#408

Merged
dcruzeneil2 merged 1 commit into
mainfrom
hypeship/escape-spt-dollar-signs
Jun 10, 2026
Merged

escape $ in stripe-projects.mdx#408
dcruzeneil2 merged 1 commit into
mainfrom
hypeship/escape-spt-dollar-signs

Conversation

@dcruzeneil2

@dcruzeneil2 dcruzeneil2 commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

the SPT spending-limit warning callout on the stripe-projects integration page rendered as a mangled math equation — mintlify interprets paired $ signs as latex/katex math mode, so **$50**. The Start-Up plan is **$200/mo** collapsed to 50**.thestart-upplanis**200/mo.

escape $ with \$ so dollar amounts render literally. fixed the same issue on the plans table (lines 16–18) and the usage-based pricing bullet (line 22) — same root cause, same file.

test plan

  • preview the page on mintlify and confirm the warning callout reads "the default spt monthly spending limit is often $50. the start-up plan is $200/mo..."
  • confirm the plans table renders dollar amounts
  • confirm the usage-based pricing bullet renders dollar amounts

note: info/pricing.mdx and integrations/stripe-projects-browser.mdx have similar unescaped $ patterns that may also render as math — left alone to keep this PR scoped, worth a follow-up.


Note

Low Risk
Documentation-only Markdown escaping with no runtime or billing behavior changes.

Overview
Escapes dollar signs in integrations/stripe-projects.mdx so Mintlify stops treating price text as LaTeX/KaTeX math and garbling the copy.

Plans table, the usage-based pricing bullet, and the SPT spending-limit <Warning> callout now use \$ for amounts (e.g. $50, $200/mo, $0.01/min) so they render as literal currency instead of broken math.

Reviewed by Cursor Bugbot for commit e03b63a. Bugbot is set up for automated code reviews on this repo. Configure here.

Mintlify interprets paired $ signs as LaTeX math mode, which mangled
the SPT spending-limit Warning callout and similarly the plans table
and usage-based pricing line. Escape $ with \$ so dollar amounts
render literally.
@dcruzeneil2 dcruzeneil2 marked this pull request as ready for review June 10, 2026 15:44
@firetiger-agent

Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: This PR only edits documentation/markdown files (stripe-projects.mdx) and does not affect any of the specified repos (kernel, infra, hypeman, hypeship) or their services.

To monitor this PR anyway, reply with @firetiger monitor this.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk assessment: Very Low.

Evidence from the diff: this PR modifies only integrations/stripe-projects.mdx, changing five literal dollar amounts to escaped \$ forms in documentation text/table cells. There are no codepath, configuration, infrastructure, permission, billing logic, or navigation changes. I found no CODEOWNERS file in the PR tree and no existing reviews via the public reviews API, so approval is appropriate for this very low-risk documentation fix.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@dcruzeneil2 dcruzeneil2 merged commit 48594e6 into main Jun 10, 2026
3 checks passed
@dcruzeneil2 dcruzeneil2 deleted the hypeship/escape-spt-dollar-signs branch June 10, 2026 15:46
@mintlify

mintlify Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🔴 Failed Jun 10, 2026, 3:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

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.

1 participant