Skip to content

Conversation

@Dargon789
Copy link
Owner

@Dargon789 Dargon789 commented Jan 19, 2026

Potential fix for https://github.com/Dargon789/interface/security/code-scanning/9

To fix the problem, we need to escape the . characters in the regular expression to ensure they match literal dots rather than any character. This will make the regular expression more precise and prevent unintended matches.

  • Locate the regular expression on line 147 and line 163 in the file apps/web/cypress/support/commands.ts.
  • Modify the regular expression to escape the . characters before gateway and uniswap.org.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

Summary by Sourcery

Bug Fixes:

  • Correct the Cypress intercept regular expression to avoid overbroad matching of GraphQL endpoint hostnames.

…ssion for hostnames

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jan 19, 2026

Deploying uniswap with  Cloudflare Pages  Cloudflare Pages

Latest commit: aaeb2ba
Status: ✅  Deploy successful!
Preview URL: https://11f55076.uniswap-omj.pages.dev
Branch Preview URL: https://alert-autofix-9.uniswap-omj.pages.dev

View logs

@codesandbox
Copy link

codesandbox bot commented Jan 19, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link

sourcery-ai bot commented Jan 19, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Cypress GraphQL intercept URL-matching regex to escape dots in the hostname so it matches only the intended Uniswap gateway domains instead of treating dots as wildcards.

File-Level Changes

Change Details Files
Tighten the Cypress intercept regex for GraphQL requests by escaping dots in the Uniswap gateway hostname.
  • Update the intercept pattern to use `(?:interface
beta).gateway.uniswap.org/v1/graphqlinstead of treating dots as wildcards in the hostname.</li><li>Ensure the regex now matches only theinterface.gateway.uniswap.orgorbeta.gateway.uniswap.org` GraphQL endpoints, preventing unintended domain matches in tests.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@gemini-code-assist
Copy link

Summary of Changes

Hello @Dargon789, 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 addresses a code scanning alert by refining a regular expression used in Cypress tests. The change ensures that the regex accurately matches specific hostnames by escaping literal dot characters, thereby improving the precision of network interception patterns.

Highlights

  • Regular Expression Fix: Escaped literal dot characters in the hostname regular expression within apps/web/cypress/support/commands.ts to prevent unintended matches and address a code scanning alert.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@snyk-io
Copy link

snyk-io bot commented Jan 19, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Repository owner deleted a comment from vercel bot Jan 19, 2026
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a minor fix to the interceptGraphqlOperation command in apps/web/cypress/support/commands.ts. The change involves escaping the literal dots in the gateway.uniswap.org domain within the cy.intercept regular expression pattern to ensure it correctly matches the intended URL. There are no review comments provided for this change.

@Dargon789 Dargon789 marked this pull request as ready for review January 19, 2026 17:04
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • Since this regex is specifically meant to match the GraphQL endpoint URL, consider anchoring it (e.g., including protocol and/or start-of-string) to avoid accidental matches on unexpected strings that merely contain the same hostname path segment.
  • If this pattern is reused elsewhere, it might be worth extracting a shared constant for the Uniswap GraphQL endpoint regex so future host changes or escape adjustments only need to be made in one place.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Since this regex is specifically meant to match the GraphQL endpoint URL, consider anchoring it (e.g., including protocol and/or start-of-string) to avoid accidental matches on unexpected strings that merely contain the same hostname path segment.
- If this pattern is reused elsewhere, it might be worth extracting a shared constant for the Uniswap GraphQL endpoint regex so future host changes or escape adjustments only need to be made in one place.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@Dargon789 Dargon789 merged commit 6ad0d16 into main Jan 19, 2026
13 of 16 checks passed
@Dargon789 Dargon789 deleted the alert-autofix-9 branch January 19, 2026 17:05
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.

2 participants