• For custom scheduler with predefined resolution order

    Ordering is defined by using a template string like the one generated in case of failure of a scheduler

    It may be something like:

    Example

    fc.schedulerFor()`
    -> [task\${2}] promise pending
    -> [task\${3}] promise pending
    -> [task\${1}] promise pending
    `

    Or more generally:

    fc.schedulerFor()`
    This scheduler will resolve task ${2} first
    followed by ${3} and only then task ${1}
    `

    WARNING: Custom scheduler will neither check that all the referred promises have been scheduled nor that they resolved with the same status and value.

    WARNING: If one the promises is wrongly defined it will fail - for instance asking to resolve 5 while 5 does not exist.

    Remarks

    Since 1.25.0

    Type Parameters

    • TMetaData = unknown

    Parameters

    Returns ((_strs: TemplateStringsArray, ...ordering: number[]) => Scheduler<TMetaData>)

      • (_strs: TemplateStringsArray, ...ordering: number[]): Scheduler<TMetaData>
      • Parameters

        • _strs: TemplateStringsArray
        • Rest ...ordering: number[]

        Returns Scheduler<TMetaData>

  • For custom scheduler with predefined resolution order

    WARNING: Custom scheduler will not check that all the referred promises have been scheduled.

    WARNING: If one the promises is wrongly defined it will fail - for instance asking to resolve 5 while 5 does not exist.

    Remarks

    Since 1.25.0

    Type Parameters

    • TMetaData = unknown

    Parameters

    • customOrdering: number[]

      Array defining in which order the promises will be resolved. Id of the promises start at 1. 1 means first scheduled promise, 2 second scheduled promise and so on.

    • Optional constraints: SchedulerConstraints

    Returns Scheduler<TMetaData>

Generated using TypeDoc