-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(error handling): add an error
event
#1585
Labels
Comments
olance
changed the title
feat(error handling): had an
feat(error handling): add an Nov 21, 2016
error
eventerror
event
Would it be ok if we just forward the |
I'm not sure we'd need more actually! |
bobylito
pushed a commit
that referenced
this issue
Dec 28, 2017
bobylito
added a commit
that referenced
this issue
Dec 29, 2017
marielaures
pushed a commit
that referenced
this issue
Dec 29, 2017
marielaures
pushed a commit
that referenced
this issue
Dec 29, 2017
bobylito
pushed a commit
that referenced
this issue
Jan 2, 2018
<a name=2.4.0></a> * **pagination:** disable buttons if not results ([#2643](#2643)) ([9017b72](9017b72)), closes [#2014](#2014) * **theme:** fix height of pagination ([#2641](#2641)) ([b3185e5](b3185e5)) * **core:** add a reload method on the InstantSearch component ([#2637](#2637)) ([e73ff13](e73ff13)) * **core:** add an error event to monitor error from Algolia ([#2642](#2642)) ([71c2d68](71c2d68)), closes [#1585](#1585) * **core:** rename `reload` to `refresh` ([#2645](#2645)) ([9b8ac65](9b8ac65)) * **wrapWithHits:** enable async init ([#2635](#2635)) ([08a8747](08a8747))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
It would be good to have an
error
event triggered by instantsearch.js when an API/network error occurs.What is the current behavior?
Right now there's no (official) way to react to any error form Algolia's side
What is the expected behavior?
Having the capability to register a handler, something like
search.on('error', (err) => { ... })
The text was updated successfully, but these errors were encountered: