The asap package (and its fork, falcor-asap) have occasionally caused issues with our build pipeline. We're not using the scheduler that relies on this package, so I'm removing it.
I kept the ASAPScheduler in the repository, in case anyone imports that file, but it simply forwards to new TimeoutScheduler(1) now. That scheduler may have slightly different behavior, but it should be similar enough for most use cases.
If you still need the exact asap behavior, there is a workaround: you can provide a custom scheduler to Falcor.Model.
Coverage increased (+0.001%) to 92.598% when pulling fac46c147001f7e92864a2df78757be2cae99813 on jcranendonk:remove-asap into 66984a89d21277f83b250b0b027cc4205bdcc63f on Netflix:master.
The asap package (and its fork, falcor-asap) have occasionally caused issues with our build pipeline. We're not using the scheduler that relies on this package, so I'm removing it.
I kept the ASAPScheduler in the repository, in case anyone imports that file, but it simply forwards to
new TimeoutScheduler(1)
now. That scheduler may have slightly different behavior, but it should be similar enough for most use cases.If you still need the exact
asap
behavior, there is a workaround: you can provide a custom scheduler to Falcor.Model.