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

Existential Amount for Cross Chain transfer #267

Merged
merged 4 commits into from
May 27, 2024
Merged

Existential Amount for Cross Chain transfer #267

merged 4 commits into from
May 27, 2024

Conversation

ap211unitech
Copy link
Contributor

@ap211unitech ap211unitech commented May 27, 2024

Description -

  1. We have to return Existential Deposit value from TransferConfig type.

  2. Update ChainType for Chain type. Add new enum EvmSubstrate in it.

export enum ChainType {
  Substrate,
  EvmSubstrate,
  Evm,
}

Summary by CodeRabbit

  • New Features

    • Introduced a new enum value EvmSubstrate to enhance chain type handling.
    • Added sourceFeeExistential to various classes for more detailed fee calculations.
  • Improvements

    • Updated destinationFee amount to 0.05 for more accurate fee representation.
    • Enhanced UI styling for better layout consistency.
  • Bug Fixes

    • Minor UI fixes related to @polkadex/thea and @polkadex/ux.
  • Refactor

    • Adjusted the order of fields in TransferConfig for better readability and organization.

@ap211unitech ap211unitech self-assigned this May 27, 2024
Copy link

changeset-bot bot commented May 27, 2024

🦋 Changeset detected

Latest commit: 68c3484

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@polkadex/thea Minor
@polkadex/ux Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

coderabbitai bot commented May 27, 2024

Walkthrough

This update introduces a new ChainType enum and integrates minor UI fixes. It also updates the destinationFee amount in the polkadex.ts configuration file and adds functionality to handle sourceFeeExistential across multiple classes. These changes ensure better mapping of chain types and accurate fee calculations for transfers.

Changes

File(s) Summary
.changeset/great-kings-mix.md Introduces a new ChainType enum and minor UI fixes.
.../substrate/config/polkadex.ts Updates amount in destinationFee from 0 to 0.05.
.../substrate/helpers.ts Updates changeSubstrateToBaseChain function to handle new ChainType mapping.
.../substrate/types.ts Adds EvmSubstrate to ChainType enum.
.../substrate/assetHub.ts, .../substrate/astar.ts, .../substrate/bifrost.ts, .../substrate/interlay.ts, .../substrate/moonbeam.ts, .../substrate/phala.ts, .../substrate/polkadex.ts, .../substrate/polkadot.ts, .../substrate/unique.ts Adds sourceFeeExistential constant and includes it in the transfer method parameters.
.../sdk/types.ts Adjusts TransferConfig type to include sourceFeeExistential before destinationFee.
.../ui/src/components/input.tsx Adds flex-1 class to a div element for better styling.

Possibly related issues

In the world of code, where changes flow,
A rabbit hops with joy to show,
New enums born, and fees aligned,
Transfers smooth, all well-defined.
With every tweak, the system grows,
In harmony, the network glows.

Tip

New Features and Improvements

Review Settings

Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments.

AST-based Instructions

CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the documentation.

Community-driven AST-based Rules

We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the ast-grep-essentials repository for more information.

New Static Analysis Tools

We are continually expanding our support for static analysis tools. We have added support for biome, hadolint, and ast-grep. Update the settings in your .coderabbit.yaml file or head over to the settings page to enable or disable the tools you want to use.

Tone Settings

Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples:

  • Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!"
  • Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!"
  • Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!"

Revamped Settings Page

We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to .coderabbit.yaml will be reflected in the settings page, and vice versa.

Miscellaneous

  • Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the enable_free_tier setting.
  • Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (local) or the organization (global) level using the knowledge_base setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations.
  • High-level summary placement: You can now customize the location of the high-level summary in the PR description using the high_level_summary_placeholder setting (default @coderabbitai summary).
  • Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the request_changes_workflow setting.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as 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 full the 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 help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@ap211unitech ap211unitech linked an issue May 27, 2024 that may be closed by this pull request
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

Outside diff range and nitpick comments (5)
packages/thea/src/sdk/substrate/interlay.ts (1)

Line range hint 51-59: Consider using for...of loops for better performance and readability when iterating over arrays.

- supportedAssets.forEach((asset) => {
+ for (const asset of supportedAssets) {

Also applies to: 69-78

packages/thea/src/sdk/substrate/polkadot.ts (2)

Line range hint 51-59: Consider refactoring the forEach loops to for...of loops for better performance and readability.

- supportedAssets.forEach((asset) => {
+ for (const asset of supportedAssets) {

Also applies to: 69-78


Line range hint 4-5: Optimize imports by using TypeScript's type-only import syntax where applicable.

- import { AnyChain } from "@moonbeam-network/xcm-types";
+ import type { AnyChain } from "@moonbeam-network/xcm-types";

Also applies to: 7-18, 18-19

packages/thea/src/sdk/substrate/polkadex.ts (2)

Line range hint 51-59: Consider refactoring the forEach loops to for...of loops for better performance and readability.

- supportedAssets.forEach((asset) => {
+ for (const asset of supportedAssets) {

Also applies to: 69-78


Line range hint 3-4: Optimize imports by using TypeScript's type-only import syntax where applicable.

- import { AnyChain, ChainType } from "@moonbeam-network/xcm-types";
+ import type { AnyChain, ChainType } from "@moonbeam-network/xcm-types";

Also applies to: 7-18, 18-19

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between f150241 and 68c3484.
Files selected for processing (15)
  • .changeset/great-kings-mix.md (1 hunks)
  • packages/thea/src/config/substrate/config/polkadex.ts (1 hunks)
  • packages/thea/src/config/substrate/helpers.ts (2 hunks)
  • packages/thea/src/config/types.ts (1 hunks)
  • packages/thea/src/sdk/substrate/assetHub.ts (2 hunks)
  • packages/thea/src/sdk/substrate/astar.ts (2 hunks)
  • packages/thea/src/sdk/substrate/bifrost.ts (2 hunks)
  • packages/thea/src/sdk/substrate/interlay.ts (2 hunks)
  • packages/thea/src/sdk/substrate/moonbeam.ts (2 hunks)
  • packages/thea/src/sdk/substrate/phala.ts (2 hunks)
  • packages/thea/src/sdk/substrate/polkadex.ts (2 hunks)
  • packages/thea/src/sdk/substrate/polkadot.ts (2 hunks)
  • packages/thea/src/sdk/substrate/unique.ts (2 hunks)
  • packages/thea/src/sdk/types.ts (1 hunks)
  • packages/ui/src/components/input.tsx (1 hunks)
Additional Context Used
LanguageTool (1)
.changeset/great-kings-mix.md (1)

Near line 6: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...d a new enum for ChainType and minor UI fix
Rule ID: AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER

Biome (52)
packages/thea/src/config/substrate/helpers.ts (2)

1-5: Some named imports are only used as types.


6-7: Some named imports are only used as types.

packages/thea/src/config/types.ts (1)

1-1: This enum declaration contains members that are implicitly initialized.

packages/thea/src/sdk/substrate/assetHub.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/astar.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/bifrost.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/interlay.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/moonbeam.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/phala.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/polkadex.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


3-4: Some named imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/polkadot.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/substrate/unique.ts (5)

51-59: Prefer for...of instead of forEach.


69-78: Prefer for...of instead of forEach.


4-5: All these imports are only used as types.


7-18: Some named imports are only used as types.


18-19: All these imports are only used as types.

packages/thea/src/sdk/types.ts (1)

1-1: All these imports are only used as types.

packages/ui/src/components/input.tsx (3)

4-14: Some named imports are only used as types.


22-23: Some named imports are only used as types.


23-24: Some named imports are only used as types.

Additional comments not posted (20)
packages/thea/src/config/types.ts (1)

3-3: The addition of EvmSubstrate to the ChainType enum aligns with the PR's objectives to support new chain types.

packages/thea/src/config/substrate/helpers.ts (1)

15-18: The updated logic in changeSubstrateToBaseChain correctly handles the new EvmSubstrate chain type.

packages/thea/src/sdk/types.ts (1)

15-16: The addition of sourceFeeExistential to TransferConfig is well-integrated and supports handling existential deposits as described in the PR.

packages/ui/src/components/input.tsx (1)

90-90: The addition of flex-1 to the Primary component enhances layout flexibility, aligning with the PR's objectives for minor UI improvements.

packages/thea/src/sdk/substrate/interlay.ts (1)

135-141: The integration of sourceFeeExistential in getTransferConfig correctly utilizes the existential deposit data, enhancing the transfer configuration capabilities.

packages/thea/src/sdk/substrate/bifrost.ts (2)

135-141: The addition of sourceFeeExistential is correctly implemented and aligns with the PR's objectives to handle existential deposits.


168-168: The inclusion of sourceFeeExistential in the transfer configuration is correctly implemented.

packages/thea/src/sdk/substrate/astar.ts (2)

135-141: The addition of sourceFeeExistential is correctly implemented and aligns with the PR's objectives to handle existential deposits.


168-168: The inclusion of sourceFeeExistential in the transfer configuration is correctly implemented.

packages/thea/src/sdk/substrate/phala.ts (2)

135-141: The addition of sourceFeeExistential is correctly implemented and aligns with the PR's objectives to handle existential deposits.


168-168: The inclusion of sourceFeeExistential in the transfer configuration is correctly implemented.

packages/thea/src/sdk/substrate/unique.ts (2)

135-141: The addition of sourceFeeExistential is correctly implemented and aligns with the PR's objectives to handle existential deposits.


168-168: The inclusion of sourceFeeExistential in the transfer configuration is correctly implemented.

packages/thea/src/sdk/substrate/assetHub.ts (2)

135-141: The addition of sourceFeeExistential is correctly implemented and aligns with the PR's objectives to handle existential deposits.


168-168: The inclusion of sourceFeeExistential in the transfer configuration is correctly implemented.

packages/thea/src/sdk/substrate/moonbeam.ts (2)

135-141: The addition of sourceFeeExistential is correctly implemented and aligns with the PR's objectives to handle existential deposits.


168-168: The inclusion of sourceFeeExistential in the transfer configuration is correctly implemented.

packages/thea/src/sdk/substrate/polkadot.ts (1)

Line range hint 135-168: The addition of sourceFeeExistential aligns with the PR's objectives and is implemented correctly.

packages/thea/src/sdk/substrate/polkadex.ts (1)

Line range hint 135-168: The addition of sourceFeeExistential aligns with the PR's objectives and is implemented correctly.

packages/thea/src/config/substrate/config/polkadex.ts (1)

155-155: The update of the destinationFee amount to 0.05 is appropriate and aligns with the PR's objectives.

@nuel77 nuel77 merged commit a961735 into main May 27, 2024
2 checks passed
@nuel77 nuel77 deleted the fix/bridge-max branch May 27, 2024 06:28
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.

Existential Amount for Cross Chain transfer
3 participants