-
Notifications
You must be signed in to change notification settings - Fork 975
Brave payments wrong contribution date #4058
Comments
i agree that the next contribution date should't be in the past. what is the correct behavior, do you think? should the browser add the length of time that brave payments was disabled to the next contribution date? or should it reset it to 30 days from the time that brave payments was last enabled? thanks! |
I think the correct behaviour should be to reset the 30 days timer from the date that you have enabled them again, just like you do for a first time. cc @bbondy for confirmation |
here's a counter-example: suppose someone switches it off and then back on again within a second or two. should the time really be reset in that case? shouldn't there be a hold-down period? |
@mrose17 It should reset only if the next contribution date is in past, not when you turn on/off the switch. For example my Next contribution date is 28 of August. If today is 1st of August it does not makes sense to increment it, since that date is in the future. But if today is 29th of August it should extend because it is in the past. Does this makes sense? |
yes, thanks! |
Fix #4058 Auditors: @mrose17 Test Plan: 1. Open Brave 2. Enable Payments then disable 2. Close Brave 3. Edit {userData}/ledger-state.json `reconcileStamp` to be way in the past (change 14.. to 13..) 4. Open Brave 5. Enable Payments 6. Note that contribution date is today + 30 days, rather than way in the past
Fix #4058 Auditors: @mrose17 Test Plan: 1. Open Brave 2. Enable Payments then disable 2. Close Brave 3. Edit {userData}/ledger-state.json `reconcileStamp` to be way in the past (change 14.. to 13..) 4. Open Brave 5. Enable Payments 6. Note that contribution date is today + 30 days, rather than way in the past
i agree with @Sh1d0w that no matter what ledger is actually doing, the UI should never say "Next contribution: |
@diracdeltas - thanks. just so i'm clear: would you be happy with "Your last contribution was due 10 days ago." @Sh1d0w - everything with respect to contributions is voluntary, and purposely so. it turns out that this allows the browser to drive the interactions entirely. that's not normally the way things are done in the payments world, but that's fine for this application! |
@mrose17 I see your point. What about the following approach:
|
What if instead of saying |
@diracdeltas - could i ask you to make the change you suggest and then close this issue, thanks! |
thanks! |
Did you search for similar issues before submitting this one?
No
Describe the issue you encountered:
I have enabled Brave payments long ago and disabled it for a while. After re-enabling it again the Next contribution date was in the past.
Expected behavior:
The next contribution date should never be in the past.
All
0.12.1
1.Enable Brave payments
- Any related issues:
The text was updated successfully, but these errors were encountered: