Skip to content

fix: relative pathing for markdown links #385

fix: relative pathing for markdown links

fix: relative pathing for markdown links #385

Triggered via pull request February 24, 2025 13:11
Status Success
Total duration 1m 27s
Artifacts

pr.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
PR
Cache not found for keys: node-cache-Linux-x64-pnpm-faacb80d3cac38ef9352a4c4142a80523fd31381ebf013e8e7a18283d520d800
PR: app/components/MarkdownLink.tsx#L8
Anchors must have content and the content must be accessible by a screen reader
PR: app/components/SponsorPack.tsx#L118
Expected '===' and instead saw '=='
PR: app/components/SponsorPack.tsx#L121
Expected '===' and instead saw '=='
PR: app/hooks/useSessionStorage.ts#L21
React Hook React.useEffect has a missing dependency: 'key'. Either include it or remove the dependency array
PR: app/routes/_libraries/config.$version.index.tsx#L33
'version' is assigned a value but never used
PR: app/routes/_libraries/index.tsx#L79
'gradient' is assigned a value but never used
PR: app/routes/_libraries/query.$version.index.tsx#L8
'TbHeartHandshake' is defined but never used
PR: app/routes/_libraries/query.$version.index.tsx#L145
Do not use <marquee> elements as they can create visual accessibility issues and are deprecated
PR: app/routes/_libraries/store.$version.index.tsx#L29
'version' is assigned a value but never used
PR: app/routes/_libraries/table.$version.index.tsx#L131
Do not use <marquee> elements as they can create visual accessibility issues and are deprecated