Skip to content

Conversation

@derrekcoleman
Copy link
Contributor

Reverts #79

@vercel
Copy link
Contributor

vercel bot commented Jun 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2025 8:20am

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Bug: API Page Detection Fails for Reference Paths

The API page detection logic incorrectly checks for params.slug?.[0] === "reference". API reference pages are actually located under the api-reference path (e.g., api-reference/endpoints/). This prevents isApiPage from being true for these pages, leading to incorrect display of the Table of Contents and edit buttons. The check should be params.slug?.[0] === "api-reference".

app/[[...slug]]/page.tsx#L58-L59

https://github.com/recallnet/docs/blob/c64e9ca5318fa39f0f27205dfb1c134cbdbaa230/app/[[...slug]]/page.tsx#L58-L59

Fix in Cursor


Bug: Image Zoom Logic and Type Safety Issues

The img component's conditional logic to disable ImageZoom is brittle, relying on hardcoded alt text string matching (e.g., "Network", "Protocol") and className patterns. This approach is prone to breakage if partner names/alt texts change or new partners are added, and it doesn't reliably detect images within Card components as intended. Additionally, the (props as any) type cast when rendering a plain <img> element bypasses TypeScript's type checking, which is unsafe as ImageZoomProps may contain properties not valid for a standard HTML <img> element, potentially leading to runtime errors or invalid HTML attributes.

app/[[...slug]]/page.tsx#L28-L45

https://github.com/recallnet/docs/blob/c64e9ca5318fa39f0f27205dfb1c134cbdbaa230/app/[[...slug]]/page.tsx#L28-L45

Fix in Cursor


Comment bugbot run to trigger another review on this PR
Was this report helpful? Give feedback by reacting with 👍 or 👎

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