You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm wondering if the JSDoc in node_modules/near-api-js/lib/account.d.ts might be incorrect. It doesn't match what is written at https://docs.near.org/concepts/basics/accounts/access-keys (which the JSDoc itself links to).
In particular, I'm looking at the methodNames and amount arguments, which say:
* @param methodNames The method names on the contract that should be allowed to be called. Pass null for no method names and '' or [] for any method names.
* @param amount Payment in yoctoⓃ that is sent to the contract during this function call
allowance: The amount of Ⓝ allowed to spend on gas (Optional). If omitted, the key will only be allowed to call view methods (read-only).
I've tried passing null for methodNames, and I think it behaves the same as when I pass []. I.e. Either way, the output of const keys = await account.getAccessKeys(); shows [] for methodNames.
Can you please let me know if I'm misunderstanding? Thanks!
The text was updated successfully, but these errors were encountered:
Hi team! 😃 ⋈ Ⓝ
Describe the bug
I'm wondering if the JSDoc in
node_modules/near-api-js/lib/account.d.ts
might be incorrect. It doesn't match what is written at https://docs.near.org/concepts/basics/accounts/access-keys (which the JSDoc itself links to).In particular, I'm looking at the
methodNames
andamount
arguments, which say:amount
wasn't calledallowance
, with this description:null
formethodNames
, and I think it behaves the same as when I pass[]
. I.e. Either way, the output ofconst keys = await account.getAccessKeys();
shows[]
formethodNames
.Can you please let me know if I'm misunderstanding? Thanks!
The text was updated successfully, but these errors were encountered: