slevithan / regex-colorizer Goto Github PK

It would be nice to be able to highlight regex comments explicitly with this, since I'm using this lib to highlight a regex that I split into parts, and indent and comment to explain. Something like the # character perhaps.

Thanks for the awesome library! I might even just do it myself and send a PR, we'll see :)

I'd prefer not to minify this library myself, especially since minifiers can introduce their own issues.

Could you provide a minified version of your code in the code base?

When using flag u, Regex Colorizer (as of v1.0.0) uses a simplistic regex to identify Unicode properties with \p{...} and \P{...}. It would be better to flag any values that are not actually supported by ECMAScript.

@mathiasbynens has a bunch of great, related libraries. See:

• unicode-match-property-ecmascript
• unicode-match-property-value-ecmascript
• unicode-property-aliases-ecmascript
• unicode-property-value-aliases-ecmascript
• unicode-canonical-property-names-ecmascript
• etc.

Not yet sure which of these are the most relevant.

The named group is the most required part.
http://xregexp.com/

• Update supported syntax to include features and escaping rules from JavaScript flag v (ES2024).
• Rewrite on top of an AST (ex: regexp-tree, regexpp).
• Consider becoming a CodeMirror mode, similar to CodeMirror PCRE mode.
  • Potentially extract RegExr's highlighting/tooltips as a starting point.
• Add more options to the options argument used by colorizeAll and colorizePattern:
  • flavor - Ex: 'JavaScript', 'EMCAScript' (alternative name: 'JavaScript-WithoutWebReality'), 'PCRE', 'XRegExp'.
    • Default: 'JavaScript'.
    • Use the latest known version for the flavor if version is not provided.
  • version - Regex flavor version. Ex: JavaScript/ECMAScript: '3', '5', '2024'; PCRE: '8.45', '10.39'.
    • Default: 'latest'.
    • Throw if unexpected value or if flavor is not provided.
    • Potential implementation: By using e.g. 'JavaScript'+'2024', it sets of bunch of feature flags, and parsing code can check for the feature flags rather than flavor/version. New flavor versions can then just augment existing objects of feature flags.
  • format - Options: '...' (default), '/.../flags', and maybe others.
    • '/.../flags' allows:
      1. Applying flags (can change syntax rules).
      2. Highlighting invalid flags/combinations and duplicates.
      3. Changing syntax rules, independent of flags: Only need to escape / in regex literals. Note: ES5 included a change to allow unescaped [/] in regex literals.
    • Throw if both format and flags are provided.
  • warningsOn - On by default? Ex: || at top level, range overflow, quantified lookaround, incomplete tokens \c,\x,\u.
  • compatibilityOn - For differences in behavior for the same syntax across regex flavors (not for when some flavors don't support a feature). Ex: Empty char classes [], [^] (JS), leading unescaped ] in char classes (non-JS).
  • suggestionsOn - Ex: Use of octals, escaped literals, [0-9] → \d (for flavors where \d is ASCII only), [\S\s] → dot with /s (if /s is active or no existing dots).
• Render whitespace characters.
• Add replacement text highlighting (also accepts options argument, with flavor, version, format).