-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 API for payment started with XMR auto conf params #7036
Conversation
It works great, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit
We can simplify the null and isEmpty
handling with Optional<String>
s. Moreover Optional
s enforce us to handle both cases and avoid NullPointerException
s.
@jmacxx are we not going to have this change implemented? |
I had to fix merge conflicts with the current master branch. Also, I don't know how to implement @alvasw suggestion above. |
From what I can see, you have implemented @alvasw, for consistency sake would it make more sense to change these checks based on your suggestions separately, when it's done for all parameters? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Fixes #7033
Basedon / follow-on from #7023.
Allows
tx-id
&tx-key
to be specified for XMR auto-confirm.