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

feat(send): add support for hex messages to send burst form #698

Merged

Conversation

blankey1337
Copy link
Contributor

@blankey1337 blankey1337 commented Sep 5, 2019

image

Adds a checkbox under advanced for 'Message is Text?'. When checked (default checked), the message is treated as text. When unchecked, the message is parsed as hex.

Closes #696. @jjos2372 💋

@codecov-io
Copy link

Codecov Report

Merging #698 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #698   +/-   ##
========================================
  Coverage    93.97%   93.97%           
========================================
  Files          115      115           
  Lines         1675     1675           
  Branches       156      156           
========================================
  Hits          1574     1574           
  Misses         101      101

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4d2f814...06b64d1. Read the comment docs.

Copy link
Member

@ohager ohager left a comment

Choose a reason for hiding this comment

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

You may shorten the assignment I commented. So, if it is not text we assume hexcode? In terms of usability could be confusing. And if it is other kind of non-textual data? The convertHex function might fail?

import {ApiService} from '../../api.service';
import {AccountService} from 'app/setup/account/account.service';
import {convertAddressToNumericId} from '@burstjs/util/out';
Copy link
Member

Choose a reason for hiding this comment

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

Nice catch

attachment = new AttachmentEncryptedMessage(encryptedMessage);
} else if (message) {
attachment = new AttachmentMessage({message, messageIsText: true});
attachment = new AttachmentMessage({message, messageIsText: messageIsText});
Copy link
Member

Choose a reason for hiding this comment

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

No need to assign messageIsText...can be shortened

@blankey1337 blankey1337 merged commit 01c233c into signum-network:develop Sep 8, 2019
@blankey1337 blankey1337 deleted the feat/deep-link-bytecode branch September 8, 2019 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Extend deeplink support
3 participants