[dadajam4]

Fixes #314.
Fixes #315.

Problem

• vue-action: navigation on click can diverge from the rendered href of the RouterLink #314: With to, the rendered href came from the RouterLink's slot, but a click navigated with router.push(to). Anything the RouterLink applied to the location (NuxtLink's trailingSlash, a wrapper that adds a locale prefix) showed in the href but not in the navigation.
• vue-action: string to breaks the hash, the query, and absolute URLs #315: A string to was parsed by hand. The hash lost its # (/a/#b → /a/b), query values were not decoded and were cut at a second =, repeated keys kept only the last value, and https: / tel: / mailto: were joined to the current path as relative paths.
• Disabled links (found while fixing the above): a disabled link kept its href and was rendered as <a disabled="true">, an attribute <a> does not have. A modifier-key click, a middle click or target still followed it, and a disabled href link without guard or onClick was followed on a plain click. With the protocol to from vue-action: string to breaks the hash, the query, and absolute URLs #315 rendered as href, this would also have applied to to.

Change

@fastkit/vue-action (minor)

• A click calls the slot's navigate() (Option B in vue-action: navigation on click can diverge from the rendered href of the RouterLink #314). It is called without the event: the click handler has already prevented its default, and Vue Router's navigate ignores such events. When the slot has no navigate, the previous router.push and registerRouteActionHandler are used. NuxtLink's custom slot provides navigate and it matches the href.
• String to: the hash keeps its #; the query goes through Vue Router's parseQuery; a to with a protocol, or a protocol-relative one, is rendered as a plain <a href>. isExternalLocation() is exported.
• A disabled link (to or href) is rendered without href, with role="link" and aria-disabled="true", and without disabled. It is not focusable, like a disabled button. Enabled links get no explicit role, since it would be redundant. Buttons keep disabled.

Impact

• registerRouteActionHandler is only called in the fallback. A handler that existed only to keep the navigation in sync with the RouterLink is no longer needed.
• Styles that select a disabled link with [disabled] no longer match; [aria-disabled='true'] does. @fastkit/vui already selects both. The changeset says this.

Verification

• New tests in packages/vue-action/src/__tests__/:
  • utils.spec.ts: the cases from vue-action: string to breaks the hash, the query, and absolute URLs #315 resolved with Vue Router, plus isExternalLocation.
  • actionable.client.spec.ts:
    • a RouterLink wrapper that appends a trailing slash: the click lands on the rendered href;
    • replace still works;
    • the handler fallback when the slot has no navigate;
    • a protocol to is rendered as a plain link;
    • disabled links with to, a protocol to and href have no href and do not navigate;
    • buttons keep disabled.
• The tests for the bugs fail against the code on main. The replace, fallback and button tests pass on both, as regression guards.
• pnpm typecheck; lint, build and tests for vue-action; typecheck and tests for vui.

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: 25ac70a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@fastkit/vue-action	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR