Add missing commas

[ezynda3]

Which Jira task belongs to this PR?

Why did I implement it this way?

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

[coderabbitai]

Walkthrough

The changes in this pull request involve modifications to the config/dexs.json file, which include the addition of several new addresses across various blockchain networks and reformatting of the bscTestnet section for proper JSON structure. Specifically, new addresses have been added to multiple network arrays, and the overall structure of the JSON file remains unchanged.

Changes

File

Change Summary

config/dexs.json

- Added address "0xbbbbbBB520d69a9775E85b458C58c648259FAD5F" in mainnet, arbitrum, aurora, avalanche, base, blast, boba, bsc, optimism, polygon, opbnb, zksync, and worldchain. - Added address "0x2321F1a63A683a1F3634Dbe1CbA0d657D5F56d54" in worldchain. - Added address "0x68D6B739D2020067D1e2F713b999dA97E4d54812" in opbnb. - Added address "0x1b02da8cb0d097eb8d57a175b88c7d8b47997506" in bscTestnet. - Reformatted bscTestnet section to ensure proper JSON structure.

Possibly related PRs

• config: addresses and signatures for sushiswap dex agg #818: This PR also modifies the config/dexs.json file by adding new addresses across various blockchain networks.
• config: add addresses and signatures for bebop #844: This PR adds the same address "0xbbbbbBB520d69a9775E85b458C58c648259FAD5F" to multiple sections in config/dexs.json.
• feat: add okx approve contract to dex #878: This PR includes the addition of the address "0x68D6B739D2020067D1e2F713b999dA97E4d54812" in the optimism section of config/dexs.json.
• fix: remove trailing comma and bad dex contract for bebop dex #880: This PR updates the config/dexs.json file with new addresses and retains existing ones.
• config: add new dodo contracts #882: This PR adds the address "0x46AFE01D758a46d64c7d8E0791314D5db3E2e683" in the opbnb section of config/dexs.json.

Suggested labels

AuditNotRequired

Suggested reviewers

• 0xDEnYO

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 88172ce and 04b1c1b.

📒 Files selected for processing (1)

• config/dexs.json (9 hunks)

🧰 Additional context used

📓 Learnings (1)

config/dexs.json (2)

Learnt from: ezynda3
PR: lifinance/contracts#861
File: config/dexs.json:748-752
Timestamp: 2024-11-21T08:39:29.530Z
Learning: In the 'worldchain' network, the addresses `0x50D5a8aCFAe13Dceb217E9a071F6c6Bd5bDB4155`, `0x8f023b4193a6b18C227B4a755f8e28B3D30Ef9a1`, and `0x603a538477d44064eA5A5d8C345b4Ff6fca1142a` are used as DEXs and should be included in `config/dexs.json`.

Learnt from: 0xDEnYO
PR: lifinance/contracts#846
File: config/dexs.json:296-300
Timestamp: 2024-11-12T09:43:10.543Z
Learning: In `config/dexs.json`, it's expected that some addresses appear multiple times across different networks.

🔇 Additional comments (4)

config/dexs.json (4)

45-45: LGTM: Consistent addition of DEX address across networks

The address 0xbbbbbBB520d69a9775E85b458C58c648259FAD5F has been consistently added across multiple networks following the established pattern.

Also applies to: 187-187, 669-669, 837-837

---

817-818: LGTM: Changes align with previous approvals

The addition of addresses to the worldchain network matches with previously approved addresses from PR#861.

---

854-856: LGTM: Improved JSON structure for bscTestnet

The bscTestnet section has been properly formatted using array notation, maintaining consistency with other network configurations.

---

Line range hint 1-865: Verify checksum format of addresses

While all addresses follow the valid Ethereum address format, it's important to verify the checksum format of the addresses to ensure integrity.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[lifi-action-bot]

Test Coverage Report

Line Coverage: 77.92% (2139 / 2745 lines)
Function Coverage: 84.00% ( 373 / 444 functions)
Branch Coverage: 37.47% ( 208 / 555 branches)
Test coverage (77.92%) is above min threshold (76%). Check passed.