Web DNS Resolver for SNS + ENS V2

[mjkid221]

Purpose

Revived an old feature from #2335 which adds Web domain name resolutions via SNS and ENS.

Understandable if the team wants to bench this while they work on other top priority items. Just wanted to get this out of the way.

[adasarpan404]

const userUUID = await this.keyringStore.activeUserKeyring()?.uuid;

It will great if you use Nullish Coalescing Operator(?) here.

[adasarpan404]

Not neccessary just saying.

[adasarpan404]

import { start } from "@coral-xyz/background";
import { supportedDomains, urlPatterns } from "../dns-redirects/constants";
import { redirect } from "../dns-redirects/helpers/tabHelper";

// Start the background process
start({
  isMobile: false,
});

// Event listener for handling URL navigation
chrome.webNavigation.onBeforeNavigate.addListener(async (details) => {
  try {
    // Extract the domain URL
    const url = new URL(details.url);
    const domainUrl = url.searchParams.get("q") || url.hostname;

    // Check if the domain URL contains spaces
    if (domainUrl && !domainUrl.includes(" ")) {
      // Redirect to the resolved URL
      await redirect(domainUrl);
    }
  } catch (error) {
    console.error("Error occurred during navigation:", error);
  }
}, {
  // Define URL patterns to match
  url: supportedDomains.flatMap((param) =>
    urlPatterns.map((pattern) => ({
      urlMatches: pattern.includes("duckduckgo")
        ? `${pattern}\\.${param}$`
        : `${pattern}\\.${param}&.*$`,
    }))
  ),
});

Instead of having two separate chrome.webNavigation.onBeforeNavigate event listeners, we can combine them into one to reduce redundancy.

[adasarpan404]

just a suggestion, please verify on your own.

[adasarpan404]

I have put an suggestion for the change in whole file for this