indonesian telephone number

.Net regular expression for resolving placeholders in the format of ${rewriter(multilevel:key)?fallback} (+ variations)

Validate and split street address (street and house number) with leading house number

Validate and split street address (street and house number) with trailing house number

Validate unicode email addresses

[ [ { "content": "_}24I:9t58Tu?m@e", "isParticipating": true, "groupNum": 0,...

This allows multiple continuous strings of only alpha numeric characters & limiting punctuation to: ?().,'+ /:@-

RegExp matches each (combined) Unicode symbol, character, or emoji consecutively. Note: there are some edge cases where it does not combine some symbols that should be seen as one symbol (after Default Grapheme Cluster Boundary of UAX #29). For Unicode code point info see codepoints.net Also, see ...

Get the python substitution strings from inside of print statements. Replace the whole substitution string with {{ ArgumentName }} for use in a Jinja2 rendering. Supports fstrings...

Extract substitution parameters from python print strings works with fstrings old style format strings old style %(variable) strings

i have paste \n after every 2-th comma using sed sed 's/\(\(*,\)\{2\}\)/\1\n/g'

Regex URL validation pattern

Regex to find URLs in text

Simple pattern for validating Cron Job descriptors in your JavaScript / TypeScript / ECMAScript projects. Includes support for date ranges, day ranges, digit ranges, divisors... all of the things you'd expect to encounter in possible Cron values.

This simply checks if the string is not empty spaces.

Original credit for this expression goes to: https://emailregex.com/

check the code

This pattern finds a parameter (sst) key + value in a GET request URL. When replaced with an empty string, effectively removes the parameter. Works with both full URLs and isolated query strings. Works in PCRE and PCRE2. Full use case: if (isset($_GET["sst"])) { // validate...

Prepare batch job for opportunity close

Need to FULLY Break Out EVERY Component of a URL? Like, as in "every constituent element individually accessible in its own named capture group?" Need it to be pre-optimized and fully ECMA-compliant? Want to see exhaustive unit tests proving these claims (144 are included; all 144 execute in 6.5ms. ...