Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Payment history footer message needs correct past/future context #6059

Closed
bradleyrichter opened this issue Dec 7, 2016 · 5 comments
Closed

Comments

@bradleyrichter
Copy link
Contributor

bradleyrichter commented Dec 7, 2016

problem: (your next contribution is 6 days ago)

image

code point:

get paymentHistoryFooter () {

Test Plan

  1. ensure that reconcileStamp in ledger-state.json is in the future - the message in about:preferences#payments should show a future contribution.

  2. set reconcileStamp to less than a day in the past - the message should indicate today.

  3. set reconcileStamp to more than a day in the past - the message should indicate overdue.

@bradleyrichter bradleyrichter modified the milestones: 0.13.3, 0.13.1 Dec 7, 2016
bkilrain added a commit to bkilrain/browser-laptop that referenced this issue Jan 13, 2017
This commit changes the tense of the payment history footer from present tense
to past tense.

Fix brave#6059

Auditors: @bsclifton

Test Plan: n/a
bkilrain added a commit to bkilrain/browser-laptop that referenced this issue Jan 13, 2017
This commit changes the paymentHistoryFooter text to match the fact that
reconcileDate will always be in the past (it is generated from moment.js's
fromNow() method).

Fixes brave#6059

Auditors: @bsclifton

Tests: n/a
@bkilrain
Copy link
Contributor

bkilrain commented Jan 13, 2017

@bsclifton Hi there - I took it upon myself to give this one a try. I've poked through the codebase and it seems that paymentHistoryFooter should always refer to an action in the past (it's the history). So I just adjusted the language to reflect that.

@luixxiul
Copy link
Contributor

luixxiul commented Jan 20, 2017

@bkilrain @mrose17 Is #6628 replaced with #6766?

@mrose17
Copy link
Member

mrose17 commented Jan 20, 2017

@luixxiul - i didn't see that PR, @bkardell - sorry!

@luixxiul - the code in #6766 is what we want because it handles each of the past/present/future cases, so #6628 should be closed without being merged...

@bsclifton
Copy link
Member

cc: the original contributor for #6628 @bkilrain (whose handle was accidentally typo'ed as @bkardell). Lots of Brians in here! ❤️

@luixxiul
Copy link
Contributor

@bkilrain sorry for typo...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.