fix: make getLinkedAgw parameters optional#419
fix: make getLinkedAgw parameters optional#419coffeexcoin merged 2 commits intoAbstract-Foundation:mainfrom
Conversation
🦋 Changeset detectedLatest commit: b14cf57 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
PR SummaryLow Risk Overview Adds a unit test that mocks Written by Cursor Bugbot for commit 791cb36. This will update automatically on new commits. Configure here. |
The
getLinkedAgwaction already falls back toclient.account?.addresswhen no address is provided, but its signature still required aGetLinkedAgwParametersobject.This makes the second argument optional so consumers can call
getLinkedAgw(client)directly, matching the existing behavior exposed throughlinkableWalletActions().getLinkedAgw()and reducing unnecessary boilerplate.Changes
parametersoptional ingetLinkedAgwRisk
Low. This is a small additive API improvement with no change to the existing fallback/error behavior.
PR-Codex overview
This PR focuses on tightening the typing of the
getLinkedAgwfunction to allow clients with hoisted accounts to call it without parameters, while requiring an address for clients without hoisted accounts. It also includes updates to related interfaces and tests.Detailed summary
LinkablePublicActionsandLinkableWalletActionsto useGetLinkedAgwActionforgetLinkedAgw.getLinkedAgwfunction signatures to support optional parameters.GetLinkedAgwParametersto conditionally requireaddress.getLinkedAgwto validate behavior with omitted parameters.