Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ideas for future redesign #6

Open
slevithan opened this issue May 13, 2024 · 0 comments
Open

Ideas for future redesign #6

slevithan opened this issue May 13, 2024 · 0 comments

Comments

@slevithan
Copy link
Owner

slevithan commented May 13, 2024

  • 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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant