Feat: Support wildcard in TWITTER_TARGET_USERS 1883

[augchan42]

Support wildcard in TWITTER_TARGET_USERS

Fixes enhancement request #1883

Summary

Added support for wildcard * in TWITTER_TARGET_USERS configuration to allow monitoring all users. This change enables broader interaction patterns while maintaining existing username validation rules.

Changes Made

• Updated username validation in twitterUsernameSchema to allow * as a special case
• Username regex now allows:
  • Leading digits (e.g., "123user")
  • Standard alphanumeric + underscore
  • Wildcard "*" character
• Added test cases to verify wildcard and numeric username support

Code Changes

// Updated username validation
.refine((username) => {
    // Allow wildcard '*' as a special case
    if (username === '*') return true;
    
    // Twitter usernames can:
    // - Start with digits now
    // - Contain letters, numbers, underscores
    return /^[A-Za-z0-9_]+$/.test(username);
}, "An X Username can only contain letters, numbers, and underscores");

Testing

• Added test cases for:
  • Wildcard "*"
  • Usernames starting with digits
  • Traditional alphanumeric usernames
  • Invalid username patterns

Related

• Supports broader monitoring capabilities
• Maintains backward compatibility with existing username patterns

[augchan42]

Oh to run the new test do pnpm i, pnpm build, then:

pnpm test client-twitter