Skip to content

Conversation

@tg339
Copy link
Member

@tg339 tg339 commented Nov 20, 2025

Note

Adds a dynamic Guides system with configurable steps, a dedicated Templates page with sidebar filters, revamped MDX/code block rendering, major nav restructure, and SEO/domain updates.

  • Guides (Dynamic)
    • New guides routing (/guides, catch-all) with manifest-driven flows (guide.toml), step discovery, and client-side builder (GuideForm, DynamicGuideBuilder).
    • Step navigation/UI (GuideStepsWrapper, TOC integration, scope selector) and content loaders (parseGuideManifest, getCachedGuideSteps).
  • Templates
    • Dedicated /templates app route with its own layout and sidebar filters (TemplatesSideNav) syncing URL params; updated grid/cards and copyable command snippet.
  • MDX & Code Blocks
    • Server-side MDX components: ServerCodeBlock, ServerFigure, ServerInlineCode, ANSI and highlight support, generic meta parsing (rehype-code-meta), improved CodeSnippet, interactive FileTree.
  • Navigation
    • Restructured MooseStack sections (OLAP, Streaming, Migrate, etc.), added Guides section; side nav expanded with nested labels and active-descendant logic.
  • Site/SEO
    • Robots and sitemaps switched to docs.fiveonefour.com with updated URLs; README docs for GITHUB_TOKEN and GitHub stars fetch supporting auth.
  • UI/Styling
    • New UI primitives (checkbox, popover, item), input/command styling tweaks, dark theme adjustments; TOC adds scope selector and "Add to Linear" button.
  • Config/Build
    • Next.js config (cacheComponents), tsconfig preset updates, Biome config added; removed app .npmrc hoist override; deps added for Radix, TanStack Form, Zod, and utilities.

Written by Cursor Bugbot for commit b953777. This will update automatically on new commits. Configure here.

@linear
Copy link

linear bot commented Nov 20, 2025

ENG-1475 Visual bugs

@vercel
Copy link

vercel bot commented Nov 20, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs-v2 Error Error Nov 28, 2025 7:47pm
framework-docs Ready Ready Preview Comment Nov 28, 2025 7:47pm

},
],
// Generic plugin to extract all meta attributes as data-* props
rehypeCodeMeta,
Copy link

Choose a reason for hiding this comment

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

Bug: Rehype plugin order causes lost metadata

The rehypeCodeMeta plugin runs after rehypePrettyCode, but rehypePrettyCode removes the data.meta property from code elements during its processing. This means rehypeCodeMeta won't find any meta attributes to extract, causing all custom code block attributes like copy, filename, variant, etc. to be silently lost. The plugin should run before rehypePrettyCode to capture the meta string before it's consumed.

Fix in Cursor Fix in Web

const paramValue = searchParams.get(option.id);
if (paramValue) {
currentValues[option.id] = paramValue;
hasGuideParams = true;
Copy link

Choose a reason for hiding this comment

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

Bug: URL language param not mapped back to form value

The form-to-URL mapping in handleLanguageChange converts form values ("ts") to URL params ("typescript"), but the URL-to-form sync in the useEffect directly uses the URL param value without reverse mapping. When the URL contains lang=typescript, this value gets set as the form field value, but the select field only accepts "ts" or "python" as valid options (per guide.toml). This causes the language select to show an invalid or empty state when navigating to a guide with lang=typescript in the URL.

Additional Locations (1)

Fix in Cursor Fix in Web

!occurrences || occurrences.includes(occurrenceCount);

if (shouldHighlight) {
return `>${prefix}<span class="highlighted-word">${pattern}</span>`;
Copy link

Choose a reason for hiding this comment

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

Bug: Substring highlighting adds duplicate angle bracket character

The applySubstringHighlighting function uses a lookbehind regex (?<=>) that asserts there's a > before the match without consuming it. However, the replacement string at line 306 starts with >, which adds a duplicate > character. Since lookbehinds don't consume characters, the original > remains in the HTML while the replacement inserts another one, corrupting the output (e.g., <span> becomes <span>>). The replacement string should not include the leading >.

Fix in Cursor Fix in Web

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