We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signUserMessage
using these versions "@onflow/fcl": "^1.4.0-alpha.8", "@onflow/typedefs": "^1.1.0-alpha.4",
const sign = await fcl.currentUser.signUserMessage(MSG); // types think that signUserMessage returns a CompositeSignature` and is not an array
const sign = await fcl.currentUser.signUserMessage(MSG);
// but in reality it is an array const [{ signature }] = sign;
expected types to match up with reality
sign a message
- OS: mac - Node: v19 - npm: 9.5
No response
The text was updated successfully, but these errors were encountered:
Fix return type #1642
dedb6cd
PKG -- [fcl/typedefs] Fix return type #1642
304fa23
PKG -- [fcl/typedefs] Fix return type #1642 (#1643)
705be3e
Hey @nialexsan , is this issue complete?
Sorry, something went wrong.
@JeffreyDoyle yes, we've merged the fix already
nialexsan
No branches or pull requests
Current Behavior
using these versions
"@onflow/fcl": "^1.4.0-alpha.8",
"@onflow/typedefs": "^1.1.0-alpha.4",
const sign = await fcl.currentUser.signUserMessage(MSG);
// types think that
signUserMessage
returns a CompositeSignature` and is not an array// but in reality it is an array
const [{ signature }] = sign;
Expected Behavior
expected types to match up with reality
Steps To Reproduce
sign a message
Environment
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered: