Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a new swap provider for Relay, focusing on EVM chains, and removes the old proxy-based implementation. A critical security vulnerability was found in the RelayClient::get_request method, where unvalidated user input in URL construction could lead to query string injection or path traversal. Further improvements are needed in error handling, logical correctness of transaction parameter mapping, and ensuring consistent support across non-EVM chains.
Add two unit tests to crates/swapper/src/relay/mapper.rs that exercise map_swap_result using RelayRequestsResponse fixtures for Base USDC -> Ethereum USDC and Base USDC -> Solana USDT. The tests assert SwapStatus::Completed and validate metadata fields (from_asset/from_value and to_asset/to_value). Add the corresponding JSON fixtures under crates/swapper/src/relay/testdata/ (request_base_usdc_to_eth_usdc.json and request_base_usdc_to_sol_usdt.json).
No description provided.