-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Remove default tip of 21% for pos custom tip #2712
Conversation
I think I'd prefer to add 21% as a placeholder AND fall back to 21% if the user thinks it's populated and submits with no value set |
Ah right, that's the perfect solution. |
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.
I think the default fees in sats should be 21% of the value, and not 2100 sats in all cases.
But using absolute amounts is the idea behind that vs. percentage...? |
Yeah, I know what you mean, but not sure if the absolute placeholder should be dynamic. What do you think @kaloudis ? |
b1de6b7
to
eef05f3
Compare
(rebased) |
I think dynamic placeholder would indeed be a nice touch |
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.
tACK
Description
This fixes #2698.
This pull request is categorized as a:
Checklist
yarn run tsc
and made sure my code compiles correctlyyarn run lint
and made sure my code didn’t contain any problematic patternsyarn run prettier
and made sure my code is formatted correctlyyarn run test
and made sure all of the tests passTesting
If you modified or added a utility file, did you add new unit tests?
I have tested this PR on the following platforms (please specify OS version and phone model/VM):
I have tested this PR with the following types of nodes (please specify node version and API version where appropriate):
Locales
Third Party Dependencies and Packages
yarn
after this PR is merged inpackage.json
andyarn.lock
have been properly updatedOther: