Update

add lazy quantifier version of original input helpers:

• add times.anyLazy, times.atLeastLazy, times.atMostLazy and times.betweenLazy under times chain helper.
• add maybeLazy and oneOrMoreLazy, two creating helpers.

Request for Input and Discussion

Lazy quantifier functionality is easy to implement, but the current naming for new helpers might not be the best naming option.

Currently, I've thought of 3 naming pattern for lazy quantifier:

1. Suffix Lazy to the name of original greedy version helpers (current implementation), eg: times.anyLazy().
   • Pro: This option group/display lazy inputs adjacent to its corresponding greedy version when shown in IDE hints/autocompletes
   • Con: not very intuitive, and might cause confusion
2. Prefix Lazy to the name of original greedy version helpers, eg: times.LazyAny().

• Pro: more intuitive compared to option 1, less confusing at conveying the functionality.
  (after some thought, I prefer this option more)

3. add an additional option argument to the input, eg: times.any({ greedy : false }) and maybe(<str>,{ greedy : false })
   • Pro: Not adding new helper inputs, less cluttering to the API
   • Con: different config style that users have to learn/know, less discoverable compare to option 1 & option 2.

need some input before finalizing the naming and adding documentation.

Usage

    const val = exactly('a').times.between(3, 5)
    const regexp = new RegExp(val as any)
    expect(regexp).toMatchInlineSnapshot('/a\\{3,5\\}\\?/')
    expectTypeOf(extractRegExp(val)).toEqualTypeOf<'a{3,5}?'>()

Resolve

resolve #228

• add/update tests
• update docs
• finalize naming