Change Details

We want to define a valid regex statement that can detect a valid ENS name that is typed out. Some requirements include: - ends in `.eth` - no spaces in the name - no special characters - the part before `.eth` should be at least 3 characters - based on the [[ https://app.ens.domains/ | ENS domain app ]], looks like underscores can start a name - hyphens seem valid Addresses [[ https://linear.app/comm/issue/ENG-5411/define-valid-regex-for-detecting-an-ens-name-is-typed | ENG-5411 ]] and [[ https://linear.app/comm/issue/ENG-5413/write-unit-tests-to-test-against-the-regex-statement | ENG-5413 ]]

We perform two checks here to ensure the validity of an ENS name that is typed in the search experiences. The first one is a general check to make sure the name adheres to the requirements listed in the [[ https://eips.ethereum.org/EIPS/eip-137#name-syntax | Ethereum spec ]]. Calling `toAscii` will throw an error if there is an invalid character, and at that point we can decide it's an invalid ENS name and not do anything special. The second check is more specific and is a requirement we're enforcing to limit the number of name-to-address lookups that need to be done. We want to ensure that the TLD is `.eth` and the SLD has //at least// three characters, as that seems to be a general standard enforced by the ENS team for now. To do this, a regex pattern is easy enough to check on the input text. If there is a match, this means we have a valid ENS name typed out in the search, and only at this point do we want to do a forward lookup. Addresses [[ https://linear.app/comm/issue/ENG-5411/define-valid-regex-for-detecting-an-ens-name-is-typed | ENG-5411 ]] and [[ https://linear.app/comm/issue/ENG-5413/write-unit-tests-to-test-against-the-regex-statement | ENG-5413 ]]

We want to define a valid regex statement that can detect a valid ENS name that is typed outperform two checks here to ensure the validity of an ENS name that is typed in the search experiences. The first one is a general check to make sure the name adheres to the requirements listed in the [[ https://eips.ethereum.org/EIPS/eip-137#name-syntax | Ethereum spec ]]. Some requirements include: - ends in `.eth` - no spaces in the name - no special characters - the part before `.eth` should be at least 3 characters - based on the [[ https://app.ens.domains/ | ENS domain app ]]Calling `toAscii` will throw an error if there is an invalid character, and at that point we can decide it's an invalid ENS name and not do anything special. The second check is more specific and is a requirement we're enforcing to limit the number of name-to-address lookups that need to be done. We want to ensure that the TLD is `.eth` and the SLD has //at least// three characters, as that seems to be a general standard enforced by the ENS team for now. To do this, a regex pattern is easy enough to check on the input text. If there is a match, looks like underscores can start a name - hyphens seem validthis means we have a valid ENS name typed out in the search, and only at this point do we want to do a forward lookup. Addresses [[ https://linear.app/comm/issue/ENG-5411/define-valid-regex-for-detecting-an-ens-name-is-typed | ENG-5411 ]] and [[ https://linear.app/comm/issue/ENG-5413/write-unit-tests-to-test-against-the-regex-statement | ENG-5413 ]]