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

Hex Encode Data in Tx Responses #4028

Merged
merged 3 commits into from
Apr 3, 2019

Conversation

alexanderbez
Copy link
Contributor

@alexanderbez alexanderbez commented Apr 2, 2019

closes: #3916


  • Targeted PR against correct branch (see CONTRIBUTING.md)

  • Linked to github-issue with discussion and accepted design OR link to spec that describes this work.

  • Wrote tests

  • Updated relevant documentation (docs/)

  • Added a relevant changelog entry: sdkch add [section] [stanza] [message]

  • rereviewed Files changed in the github PR explorer


For Admin Use:

  • Added appropriate labels to PR (ex. wip, ready-for-review, docs)
  • Reviewers Assigned
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

@alexanderbez alexanderbez added the T: API Breaking Breaking changes that impact APIs and the SDK only (not state machine). label Apr 2, 2019
@codecov
Copy link

codecov bot commented Apr 2, 2019

Codecov Report

Merging #4028 into develop will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           develop    #4028   +/-   ##
========================================
  Coverage    60.02%   60.02%           
========================================
  Files          212      212           
  Lines        15104    15104           
========================================
  Hits          9066     9066           
  Misses        5417     5417           
  Partials       621      621

if r.Data != nil {
sb.WriteString(fmt.Sprintf(" Data: %s\n", string(r.Data)))
if r.Data != "" {
sb.WriteString(fmt.Sprintf(" Data: %s\n", r.Data))
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we use tab \t in this function?

Suggested change
sb.WriteString(fmt.Sprintf(" Data: %s\n", r.Data))
sb.WriteString(fmt.Sprintf("\tData: %s\n", r.Data))

Copy link
Contributor

Choose a reason for hiding this comment

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

oh no, please don't.... I'd even remove the trailing \n

Copy link
Contributor Author

@alexanderbez alexanderbez Apr 3, 2019

Choose a reason for hiding this comment

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

lol...the tab vs space war begins. idc really (go's standard is tabs actually), but I'd rather be consistent. What to do?

Copy link
Member

Choose a reason for hiding this comment

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

plz no \t 🙏

Copy link
Contributor

@alessio alessio left a comment

Choose a reason for hiding this comment

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

ACK

@alexanderbez alexanderbez changed the base branch from develop to release/v0.34.0 April 3, 2019 14:49
@jackzampolin jackzampolin merged commit 0e55b6e into release/v0.34.0 Apr 3, 2019
@jackzampolin jackzampolin deleted the bez/3916-fix-data-tx-resp branch April 3, 2019 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: API Breaking Breaking changes that impact APIs and the SDK only (not state machine).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants