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

fixed WALLET_PROPERTIES_ST serialization #2228

Merged
merged 2 commits into from
Apr 17, 2019
Merged

Conversation

SergeyZhukovsky
Copy link
Member

@SergeyZhukovsky SergeyZhukovsky commented Apr 16, 2019

closes brave/brave-browser#4115

Submitter Checklist:

  • 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
    • Android
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security) on
    • Windows
    • macOS
    • Linux
  • Verified that all lint errors/warnings are resolved (npm run lint)
  • 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:

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

writer->String(data.probi_.c_str());

writer->String("balance");
writer->Double(data.balance_);
writer->String(std::to_string(data.balance_).c_str());
Copy link
Collaborator

@tmancey tmancey Apr 16, 2019

Choose a reason for hiding this comment

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

I agree using a String is safer, however right now the solution to be consistent would be to change d.HasMember("balance") && d["balance"].IsString() to d.HasMember("balance") && d["balance"].IsDouble()

@NejcZdovc Would be great if you could check the above

Copy link
Member Author

Choose a reason for hiding this comment

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

I think we discussed on a call that we are going to change all double to string internally. I don't think we should change it there.

Copy link
Contributor

Choose a reason for hiding this comment

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

structure currently have it as string so we should leave it as string for now

@tmancey tmancey self-requested a review April 17, 2019 14:02
@tmancey
Copy link
Collaborator

tmancey commented Apr 17, 2019

LGMT to me other than comment to @NejcZdovc, also @SergeyZhukovsky can you tick the appropriate boxes in the description please, thanks

@SergeyZhukovsky
Copy link
Member Author

I marked the checkboxes and commented on the above question to @NejcZdovc

Copy link
Collaborator

@tmancey tmancey left a comment

Choose a reason for hiding this comment

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

Approving to unblock Android team. @NejcZdovc if there is anything you notice can you please create a follow up issue

@SergeyZhukovsky SergeyZhukovsky merged commit fda3742 into master Apr 17, 2019
@NejcZdovc NejcZdovc deleted the insufficient_funds branch April 17, 2019 17:26
@NejcZdovc NejcZdovc added this to the 0.65.x - Nightly milestone Apr 17, 2019
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.

Insufficient funds message immediately after auto contribution
4 participants