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: javascore dapp new message type #248

Conversation

gcranju
Copy link
Collaborator

@gcranju gcranju commented Jan 22, 2024

Description:

Commit Message

feat: javascore dapp new message type

see the guidelines for commit messages.

Changelog Entry

version: <log entry>

Checklist:

  • I have performed a self-review of my own code
  • I have documented my code in accordance with the documentation guidelines
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have run the unit tests
  • I only have one commit (if not, squash them into one commit).
  • I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Copy link

codecov bot commented Jan 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (df65822) 69.33% compared to head (331a188) 69.33%.
Report is 1 commits behind head on development/177-xcall-future-proof-messaging.

Additional details and impacted files

Impacted file tree graph

@@                               Coverage Diff                               @@
##             development/177-xcall-future-proof-messaging     #248   +/-   ##
===============================================================================
  Coverage                                           69.33%   69.33%           
  Complexity                                             64       64           
===============================================================================
  Files                                                  40       40           
  Lines                                                2195     2195           
  Branches                                               24       24           
===============================================================================
  Hits                                                 1522     1522           
  Misses                                                663      663           
  Partials                                               10       10           
Flag Coverage Δ
solidity 82.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Copy link
Collaborator

@AntonAndell AntonAndell left a comment

Choose a reason for hiding this comment

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

Looks good.
But also implement response: #245 (review)

@gcranju gcranju requested a review from AntonAndell January 24, 2024 07:41

if (new String(_data).equals("reply-response")) {
// response message
_sendCallMessage(Context.getValue(), _from, new byte[] { 1, 2, 3 }, null);
Copy link
Collaborator

Choose a reason for hiding this comment

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

User BigInteger.ZERO instead of Context.getValue. Just so it clear that it is supposed to be free

Copy link
Collaborator

@AntonAndell AntonAndell left a comment

Choose a reason for hiding this comment

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

Looks good

@AntonAndell AntonAndell merged commit 7b50c81 into development/177-xcall-future-proof-messaging Jan 24, 2024
13 of 14 checks passed
@AntonAndell AntonAndell deleted the feat/javascore-dapp-new-message-type branch January 24, 2024 08:09
bishalbikram pushed a commit that referenced this pull request Oct 2, 2024
* feat: new Message type added in javascore

* feat: new Message type added in javascore dapp

* fix: unallowed method removed

* feat: sendMessageAny added in javascore

* fix: message type added in dapp

* feat: add response ability

* fix: set response value sent zero
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature iBriz iBriz Filter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants