Suggestion to use raw template literals for parity with native syntax

[webstrand]

In your readme example

const groups2 = typedRegExp('^(?<year>\\d{4})-(?<month>\\d{2})-(?<day>\\d{2})$', 'g').exec('2000-10-24')!.groups;

the complicated and error-prone escaping can be made simpler by using String.raw (or the equivalent TemplateStringsArray#raw

const groups2 = typedRegExp(String.raw`^(?<year>\d{4})-(?<month>\d{2})-(?<day>\d{2})$`, 'g').exec('2000-10-24')!.groups;

allowing you to keep the same syntax as in the native regex, making it easy to transform from one form to the other.

You could adapt an api like typedRegExp`^(?<year>\d{4})-(?<month>\d{2})-(?<day>\d{2})$`.g.exec("2000-10-24")!.groups to make it seamless. I haven't thought enough about it to decide if that's a good idea or not.

[codpro2005]

I never considered this and I think your idea is excellent! I’ll have to play around with it, since I haven’t worked with String.raw & tagged template literals so far. That said, I think I’m likely going to add it.

I will most likely not deprecate the current implementation since it's a normal function offering a familiar API and instead provide the tagged template literal as an alternative API acting as a clean "shorthand". I'm also considering making a slight change to the flag input for the tagged template literal, using currying:

regex`^(?<year>\d{4})-(?<month>\d{2})-(?<day>\d{2})$`('g').exec('2000-10-24')`

Additionally, I'll encourage String.raw for any usage of the current implementation.

None of this is set in stone, I'll give it more time once I'm back from vacation. If you or anyone else has any feedback to my input, I'd love to hear it. Thank you for this great suggestion!

[codpro2005]

Hello

Surprisingly, this doesn't seem to be possible right now since the raw template literal isn't inferable inside custom tagged template literals. String.raw doesn't work either:

const raw = String.raw`\d`;
//    ^? const raw: string
const taggedArgs = (<TArgs extends unknown[]>(...args: TArgs) => args)`\d`;
//    ^? const taggedArgs: [TemplateStringsArray]

There’s ongoing discussion about stricter typing for TemplateStringsArray in this issue and pull request.

So this issue currently faces the same limitation as #1.

It's also worth noting that using a custom tagged template literal may stretch the intended use of tagged templates, since no custom logic is applied and it’s only a shortcut for String.raw. That said, I’d still be interested in supporting this once TypeScript resolves the underlying typing issue, as it would improve the developer experience.

Please let me know if I missed anything or if you know of any workarounds.