Skip to content
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

Upgrading brave-ui -> 0.34.6 #979

Merged
merged 1 commit into from
Nov 29, 2018
Merged

Upgrading brave-ui -> 0.34.6 #979

merged 1 commit into from
Nov 29, 2018

Conversation

ryanml
Copy link
Contributor

@ryanml ryanml commented Nov 29, 2018

Submitter Checklist:

Fixes: brave/brave-browser#2277

Contains the following updates:
Fixes console error concerning use of fill-rule
Fixes missing data-test-id from welcome page opt-in button

It should be verified that browser tests are passing with this PR

  • 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).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
    • Windows
    • macOS
    • Linux
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.
  • Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

  1. Checkout the branch
  2. rm -rf node_modules && npm i
  3. Fresh profile
  4. Launch Brave
  5. Visit brave://rewards
  6. Inspect Yes, I'm in! button
  7. Should have data-test-id='optInAction'

Automated test plan

npm run test brave_browser_tests

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

@ryanml ryanml self-assigned this Nov 29, 2018
@ryanml ryanml changed the title Fixes brave/brave-browser#2277, brave-ui -> 0.34.6 Upgrading brave-ui -> 0.34.6 Nov 29, 2018
petemill
petemill previously approved these changes Nov 29, 2018
@@ -304,7 +304,7 @@ export class Panel extends React.Component<Props, State> {
platform={publisher.provider as Provider}
publisherName={publisher.name}
publisherImg={faviconUrl}
monthlyAmount={10}
monthlyAmount={'10.0'}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is changed here to a string float to accommodate an update in brave-ui to monthlyAmount type.

Currently nothing is done with monthlyAmount but will work as of: #957

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.

Inspected element; looks good!
screen shot 2018-11-28 at 8 06 21 pm

All browser tests passed 😄 👍
SUCCESS: all tests passed.

@bsclifton bsclifton merged commit f5720e9 into brave:master Nov 29, 2018
bsclifton added a commit that referenced this pull request Nov 29, 2018
Upgrading brave-ui -> 0.34.6
@bsclifton
Copy link
Member

master f5720e9
0.58.x 9f7b599

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

Successfully merging this pull request may close these issues.

Browser tests are failing on master
4 participants