Expose XHR - Intercept remote calls.

[awgeorge]

It seems like this plugin is locked down. Its a shame that twitter didn't allow for customisation.

I am now finding very difficult to intercept the XHR request. The typeahead sometimes responds with 401 if your session has timed out. I would like to intercept it and return the user to the login screen.

I have tried:

$(document).ajaxComplete(function(event, xhr) {
        if(xhr.status == 401){
            window.location.reload();
        }
    });

.bind('typeahead:asyncreceive', function(event , a ,b){
        //none of these vars are useful. - event object doesn't seem to contain the XHR

    });

I have also tried numerous settings in bloodhound / typeahead, but these appear to have been phased out:
twitter/typeahead.js#1029
http://stackoverflow.com/questions/23985898/twitter-typeahead-bloodhound-reutilization-how-do-i-show-a-loading-gif-for-th

Starting to wish I picked a different library :/

[jlbooker]

This would also be useful for catching/handling other errors as well. For example, if search suggestions cannot be provided from the server due to some internal error. Instead of just showing zero suggestions, I'd like the chance to catch that error and show a message to the user.

I suspect you could workaround this in the short term by implementing your own source object (i.e. replace Bloodhound, or fork and extend it).

Ideally though, we'd add this to Bloodhound as an optional callback method that is called when the XHR status is anything other than 200 OK. This would allow 401, 404, and 500 status codes (and others) to be caught and handled by the developer.

[sheeley]

I ran into the same issues, and like you suggested, countered by building my own source. To be honest, I never understood why they had built it as an integrated piece, I always preferred to write my own logic there.

Anyhow, it sounds like you may be up for sending a PR to add the logic you're looking for - are you?

[jlbooker]

@sheeley I'd certainly welcome a PR. I'd want to consult some of the more active maintainers too (@jesperronn, maybe?).