That being said it feels like chaos will ensue if you try to mix and match.


On Tue, May 7, 2013 at 3:26 PM, Kevin Decker <kevin@setdirection.com> wrote:

> Unless we can justify a use case we shouldn't add code. If someone is bit
> by it they can always send a PR and explain the use case that we didn't see
> :)
>
>
> On Tue, May 7, 2013 at 3:23 PM, Joe Hudson <notifications@github.com>wrote:
>
>> In src/loading.js:
>>
>> > @@ -296,6 +296,17 @@ function fetchQueue(options, $super) {
>> >      // WARN: Should ensure that loaders are protected from out of band data
>> >      //    when using this option
>> >      this.fetchQueue = undefined;
>> > +  } else if (this.fetchQueue) {
>> > +    // concurrent set/reset fetch events are not advised
>> > +    var reset = (this.fetchQueue[0] || {}).reset;
>> > +    if (reset !== options.reset) {
>> > +      if (Thorax.loadHandler.allowMixedFetch) {
>>
>> Mostly to be pluggable. Given that this is an OSS project, I didn't just
>> want to override default behavior without some way of undoing our override
>> (w/o copy/pasting the entire method)
>>
>> —
>> Reply to this email directly or view it on GitHub<https://github.com/walmartlabs/thorax/pull/147/files#r4122012>
>> .
>>
>
>