You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this dose the exact same thing, (I have not tested the code - it's a proposal, that i think i got right)
resolve(cb){cb=cb||(()=>{});constiterator=this.conflicts.values();constresolveConflicts=iterator=>{const{value:conflict, done}=iterator.next();// use this line if this.conflicts.entries() is being used instead// const {value:[i, conflict], done} = iterator.next();if(done)cb();elseif(!conflict)resolveConflicts();elsethis.collision(conflict.file,status=>{// Remove the resolved conflict from the queue_.pull(this.conflicts,conflict);conflict.callback(null,status);resolveConflicts(iterator);});};resolveConflicts(iterator);}
i saw over at node.green that array.values() was not so widely compatible but .entries() was so i also showed how to destruct using entries (also possible to remove destructing all together...)
The text was updated successfully, but these errors were encountered:
The
async
lib are huge and you only use one function (series) at one placegenerator/lib/util/conflicter.js
Line 4 in b1e62ec
generator/lib/util/conflicter.js
Lines 71 to 91 in b1e62ec
I believe this dose the exact same thing, (I have not tested the code - it's a proposal, that i think i got right)
i saw over at node.green that
array.values()
was not so widely compatible but.entries()
was so i also showed how to destruct using entries (also possible to remove destructing all together...)The text was updated successfully, but these errors were encountered: