Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/runtime/components/Link.vue`:
- Around line 177-182: The existing localized-check in the Link component (using
i18n, localeCodes, path and localePath) fails to recognize localized paths that
include query or hash fragments (e.g. "/fr?x=1" or "/fr#top"), causing
double-prefixing; update the condition that currently tests path === `/${code}`
or path.startsWith(`/${code}/`) to also treat paths starting with `/${code}?` or
`/${code}#` as already localized (or use a single regex like
^/${code}(?:$|[/?#])) so the function returns the original path when matched,
otherwise fall back to calling localePath(path, props.locale).
---
Nitpick comments:
In `@src/runtime/components/Link.vue`:
- Around line 87-95: Add an explicit JSDoc `@defaultValue` for the locale prop and
ensure the runtime prop default matches it: update the locale prop JSDoc in
Link.vue to include "@defaultValue undefined" (or "@defaultValue true" if you
prefer documenting behavior as auto-localize) and set the runtime default using
withDefaults around defineProps (e.g., withDefaults(defineProps<{ locale?:
boolean | string }>(), { locale: undefined })) so the documented default and
actual runtime default for the locale prop are aligned.