fix: use next/link for internal navigation#264
Conversation
Greptile SummaryConverts raw
Confidence Score: 5/5Safe to merge — all changes are minimal, targeted link replacements with no logic modifications. Every changed line is either a → swap on an internal route or a Prettier reformat. The Link import is already present in the files that needed it, and the mailto: anchors are correctly left untouched. There are no logic changes, data flow modifications, or new dependencies introduced. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["User on blog/for-hire/gigs/investors page"] --> B{"Link type?"}
B -->|"Internal route (/blog, /gigs, /for-hire, /funding, /mcp)"| C["next/link <Link>\n(client-side navigation, prefetch)"]
B -->|"External / mailto:"| D["Plain <a> tag\n(full page reload / email client)"]
C --> E["No ESLint no-html-link-for-pages warning"]
D --> F["Normal browser behaviour preserved"]
Reviews (1): Last reviewed commit: "fix: use next links for internal navigat..." | Re-trigger Greptile |
Submitted for the active Ugig request to test the repo, file bugs, and submit PR fixes: https://ugig.net/gigs/abd6b2a0-e728-48cf-a46f-f99e419ed94e
Bug report: #263
Fix:
<a href="/...">links withnext/linkin the blog detail back link, gigs/for-hire cross-links, and investor page CTA links.mailto:investor contact link as a normal anchor.@next/next/no-html-link-for-pageswarnings for these routes.Validation:
pnpm exec prettier --check src/app/blog/[slug]/page.tsx src/app/for-hire/[[...tags]]/page.tsx src/app/gigs/[[...tags]]/page.tsx src/app/investors/page.tsxpnpm exec eslint src/app/blog/[slug]/page.tsx src/app/for-hire/[[...tags]]/page.tsx src/app/gigs/[[...tags]]/page.tsx src/app/investors/page.tsxpnpm type-checkpnpm lintnow reports 39 warnings instead of the 45-warning baseline; the internal page-link warnings fixed here are gone. Remaining warnings are pre-existing and unrelated.