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

Payments features 1.0 #7642

Merged
merged 5 commits into from
Mar 30, 2017
Merged

Conversation

NejcZdovc
Copy link
Contributor

@NejcZdovc NejcZdovc commented Mar 9, 2017

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Ran git rebase -i to squash commits (if needed).

Resolves #7347

Auditors

@bsclifton @bradleyrichter @mrose17 @alexwykoff

Test plan

@NejcZdovc NejcZdovc added this to the 0.13.6 milestone Mar 9, 2017
@NejcZdovc NejcZdovc self-assigned this Mar 9, 2017
@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch from 819f9fd to b9c3e58 Compare March 12, 2017 07:12
@NejcZdovc NejcZdovc modified the milestones: 0.13.7, 0.13.6 Mar 12, 2017
@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch from b9c3e58 to a24b1b2 Compare March 14, 2017 12:02
@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch 11 times, most recently from 921aa3d to 52a9ec3 Compare March 21, 2017 08:33
@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch 2 times, most recently from a8b397f to 132de84 Compare March 22, 2017 09:48
@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch 7 times, most recently from dfcd1ea to 4239016 Compare March 23, 2017 14:23
@mrose17
Copy link
Member

mrose17 commented Mar 23, 2017

many thanks!

@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch from 27a7be0 to 2bf1018 Compare March 23, 2017 23:30
Resolves brave#7347
Resolves brave#6890

Auditors: @bsclifton @bradleyrichter @mrose17

Test plan:
- npm run test -- --grep="LedgerTable"
- npm run test -- --grep="Ledger table"
@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch from 2bf1018 to a404201 Compare March 23, 2017 23:33
Copy link
Contributor

@cezaraugusto cezaraugusto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: if I pin a website I can't change enabled state anymore until I unpin, is that intentional?

@bradleyrichter
Copy link
Contributor

@cezaraugusto yes. Although I don't know which is easier to understand for usability. We could leave the switch enabled and allow a pinned site to be "excluded" which would be a macro for "un pin and set to zero %.

@NejcZdovc NejcZdovc force-pushed the feature/#7347-payment-features branch 5 times, most recently from 863d582 to 385f5f8 Compare March 25, 2017 14:34
Copy link
Member

@mrose17 mrose17 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Copy link
Member

@bsclifton bsclifton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests look good- I tried it out earlier and everything had worked as expected 😄 Great job on this one!

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

Successfully merging this pull request may close these issues.

6 participants