-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
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
Add access to approve session properties #271
Add access to approve session properties #271
Conversation
Hello @hmendez-figure, thanks for opening! I'll check this PR as soon as I can, in the meantime could you add in the description and explanation on why is this needed? Thanks! |
Quality Gate passedIssues Measures |
Quality Gate passedIssues Measures |
Hi @quetool, was there anything else needed or any concerns holding up this pull request? Our organization has taken to forking the repo to solve the problem about not having access to |
Hello @VigM-Figure! Actually thanks for the ping! I will take care of this soon! Thanks! |
Hello @hmendez-figure, do you mind trying test on your end and fix then if any? Thanks! |
Never mind! I will just merge it and take care of it on my end! Thanks @hmendez-figure @VigM-Figure for this and sorry for the huge delay! It will be deployed on the next release! 👌 |
Description
Allows full access to
SignEngine.approveSession
(specificallysessionProperties
) params from interfaces.dApp and wallet are able to send optional
sessionProperties
via Proposal and Settlement messages according to spec. Currently the dApp client exposes this viaconnect()
but wallet client does not inapproveSession
even thoughSignEngine.approveSession
in fact does implement it. Though the interface (ISignEngineWallet
) does not expose it.I compared this to the JS sign client and it also exposes it here
Resolves # (issue)
How Has This Been Tested?
Smoke Test
Due Dilligence