[v2] Match tokens via named capturing groups #3924

LeaVerou · 2025-05-01T06:29:28Z

Prism's token syntax is helpful for certain things, but for other use cases a single regex with named capturing groups can be easier.
I propose we just use all named capturing groups as token names (automatically converted to kebab-case)
If that becomes a problem, we can introduce a setting to ignore some of them.

This can be combined with regular tokens, they'd just operate on the unmatched text. The tokens matched in the regex can also be specified again in the literal if we want to specify inside or $language. E.g. imagine something like this for the markdown code blocks:

'code-block': {
	pattern: /^```(?<codeLanguage>[a-z-]+).+(?:\n|\r\n?)(?<code>[\s\S]*)?(?:\n|\r\n?)```$/i,
	'punctuation': /```/,
	'code': {
		$language: groups => groups.codeLanguage,
	}
}

Note that this means inside can also be a regex now.

Here's a more substantial example: 586bd55

The text was updated successfully, but these errors were encountered:

LeaVerou added v2 and removed v2 labels May 1, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[v2] Match tokens via named capturing groups #3924

[v2] Match tokens via named capturing groups #3924

[v2] Match tokens via named capturing groups #3924

[v2] Match tokens via named capturing groups #3924

Comments

Uh oh!