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(xrpl): custom definitions support #2683

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

elmurci
Copy link
Contributor

@elmurci elmurci commented Apr 23, 2024

High Level Overview of Change

In previous versions, custom definition support was added to the ripple-binary-codec methods but not the proxy ones in the xrpl package.

This PR adds support for Custom Definitions to the following xrpl methods:

  • utils.encode
  • utils.decode
  • utils.encodeForSigning
  • Wallet.sign
  • client.submit() (@tequdev)
  • client.submitAndWait (@tequdev)

Context of Change

When using custom definitions, you had to directly use the encode, decode, and encodeForSigning methods from ripple-binary-codec. Those features can now be used via the proxy methods in the xrpl package.

Custom definition support has also been added to the Wallet.sign method which wasn't the case before.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Tests (You added tests for code that already exists, or your new feature included in this PR)
  • Documentation Updates
  • Release

Did you update HISTORY.md?

  • Yes
  • No, this change does not impact library users

Test Plan

Added 3 unit tests for:

  • Wallet.sign (single signature)
  • Wallet.sign (multisignature)
  • Wallet.sign (unknown transaction type)

@elmurci elmurci marked this pull request as ready for review April 23, 2024 12:51
@justinr1234
Copy link
Collaborator

Hey there, did you also check #2214

@mvadari
Copy link
Collaborator

mvadari commented Apr 23, 2024

Hey there, did you also check #2214

#2214 is massively outdated and it'd take a ton of effort to update.

@mvadari mvadari requested review from khancode and pdp2121 May 7, 2024 16:37
@tequdev
Copy link
Contributor

tequdev commented Aug 24, 2024

@elmurci

I have created a PR for client.submit() and client.submitAndWait() to support definitions as well.
If it looks good, please consider including it in this PR.

elmurci#1

…n_support

Support custom definitions for `client.submit()`, `client.submitAndWait()`
@elmurci
Copy link
Contributor Author

elmurci commented Aug 26, 2024

@elmurci

I have created a PR for client.submit() and client.submitAndWait() to support definitions as well. If it looks good, please consider including it in this PR.

elmurci#1

done, thanks @tequdev

@mvadari mvadari linked an issue Aug 28, 2024 that may be closed by this pull request
@mvadari
Copy link
Collaborator

mvadari commented Sep 4, 2024

@elmurci looks like something broke TS

Copy link
Contributor

@tequdev tequdev left a comment

Choose a reason for hiding this comment

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

Applying this change resolved the build error (in my local).

packages/xrpl/src/client/index.ts Outdated Show resolved Hide resolved
@tequdev
Copy link
Contributor

tequdev commented Sep 13, 2024

@elmurci
Here is a commit that fixes the current lint error.
Please use it if necessary.

tequdev@4f93aa8

@justinr1234
Copy link
Collaborator

@coderabbitai full review

Copy link

coderabbitai bot commented Sep 19, 2024

Actions performed

Full review triggered.

Copy link

coderabbitai bot commented Sep 19, 2024

Warning

Rate limit exceeded

@justinr1234 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 29 minutes and 55 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between f3960c3 and 2c60a1e.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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.

Full custom definition support
5 participants