-
Notifications
You must be signed in to change notification settings - Fork 1
Update manufacturer back link destination #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughBackLink usage in manufacturer page templates and one manufacturer doc was updated: the link target is Changes
Sequence Diagram(s)(No sequence diagram: changes are text/link updates and do not affect control flow.) Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/scripts/generateManufacturerPages.ts (1)
6-11: Consider migrating to ES modules for TypeScript.This
.tsfile uses CommonJS syntax (require,module.exports) instead of ES module syntax (import,export). For TypeScript files, ES modules are the standard and provide better type inference and tree-shaking.Apply this diff to migrate to ES modules:
-const fs = require("fs"); -const path = require("path"); -const { - fetchManufacturers, - enrichManufacturersWithDeviceTypes, -} = require("./fetchManufacturers"); +import fs from "fs"; +import path from "path"; +import { + fetchManufacturers, + enrichManufacturersWithDeviceTypes, +} from "./fetchManufacturers";And at the end of the file:
-module.exports = { generateManufacturerPage, generateIndexPage }; +export { generateManufacturerPage, generateIndexPage };
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
scripts/generateManufacturerPages.js(1 hunks)src/scripts/generateManufacturerPages.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{ts,tsx}
📄 CodeRabbit inference engine (CLAUDE.md)
**/*.{ts,tsx}: Naming: Use PascalCase for components and camelCase for functions/variables
Imports: Group imports by order — React, external dependencies, internal components, then assets
Files:
src/scripts/generateManufacturerPages.ts
🔇 Additional comments (2)
scripts/generateManufacturerPages.js (1)
493-493: LGTM - BackLink update is consistent.The BackLink update matches the change in
src/scripts/generateManufacturerPages.ts, ensuring consistency across both script versions.Note: The two generator scripts (
src/scripts/generateManufacturerPages.tsandscripts/generateManufacturerPages.js) have significantly different implementations (this JS version includes extensive styling and hero sections, while the TS version has a minimal template). While this is outside the scope of the current change, consider consolidating these implementations in the future to reduce maintenance overhead.src/scripts/generateManufacturerPages.ts (1)
66-66: Approve path update Verified that docs/integrations/manufacturers/devices-and-oems.md exists and no references to/integrations/manufacturers/supported-manufacturersremain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (3)
docs/integrations/manufacturers/emporia.md(1 hunks)scripts/generateManufacturerPages.js(1 hunks)src/scripts/generateManufacturerPages.ts(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- src/scripts/generateManufacturerPages.ts
🚧 Files skipped from review as they are similar to previous changes (1)
- scripts/generateManufacturerPages.js
🧰 Additional context used
📓 Path-based instructions (2)
{docs/**,src/components/**}
📄 CodeRabbit inference engine (CLAUDE.md)
Content Structure: Follow Docusaurus conventions by placing docs in docs/ and components in src/components/
Files:
docs/integrations/manufacturers/emporia.md
{docs/**/*.{md,mdx},**/*.tsx}
📄 CodeRabbit inference engine (CLAUDE.md)
Links: Use relative paths for internal navigation
Files:
docs/integrations/manufacturers/emporia.md
| import { BackLink } from '@components/BackLink'; | ||
|
|
||
| <BackLink to="/integrations/manufacturers/devices-and-oems" label="Devices & OEMs" /> | ||
| <BackLink to="/integrations/manufacturers/devices-and-oems" label="Back to Supported Manufacturers" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use a relative BackLink target
Docs guidelines require internal links to be relative. Swap the absolute /integrations/manufacturers/devices-and-oems for a relative path so navigation stays guideline-compliant.
Apply this diff:
-<BackLink to="/integrations/manufacturers/devices-and-oems" label="Back to Supported Manufacturers" />
+<BackLink to="./devices-and-oems" label="Back to Supported Manufacturers" />📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <BackLink to="/integrations/manufacturers/devices-and-oems" label="Back to Supported Manufacturers" /> | |
| <BackLink to="./devices-and-oems" label="Back to Supported Manufacturers" /> |
🤖 Prompt for AI Agents
In docs/integrations/manufacturers/emporia.md around line 8, the BackLink target
currently uses an absolute path (/integrations/manufacturers/devices-and-oems);
replace it with a relative path (e.g., ../devices-and-oems or
../manufacturers/devices-and-oems as appropriate for the docs structure) so the
internal link is relative and conforms to docs guidelines.
Summary
Testing
https://chatgpt.com/codex/tasks/task_b_68f143a8a19883328d53b7c93224e0e6