Default and customizable error messages

Hello, I’d like to be able to have a default notifications in case of service errors while being able to override it if I want to notify the user with custom messages.

As a starting point I’ve overridden the errorInterceptor in my configure stage of the app:

App.config ['RestangularProvider', (RestangularProvider) ->
  RestangularProvider.setErrorInterceptor (response, promise) ->
    toastr.error 'There has been an error contacting the server, please try again'
]

This way on every error toastr shows the default notification. Now, since I want to be able to override the message or do custom actions, I’ve tried to use the promise trying to get it returned valued using promise.reject() so in my controllers I could:

UserService.get('me').then (user) ->
    $scope.user = user
    $scope.userLoading = false
  , ->
    toastr.error 'There has been an error loading the current user!'
    false

and checking the return value in my default error handling I’m able to skip the default behaviour. However from promise.reject() I always get undefined as result, is there a way to achieve this?

[btiernay]

@mgonto Why not run the local error handlers first, before the global handler? This is how most web frameworks work as it allows the local context to override the default global context.

[RafaelVidaurre]

I’m having this issue too. I think that the errorInterceptor should somehow be able to tell whether the re’s a reject callback for the promise defined for a particular request. That way we could avoid handling an error if it’s being customly handled somewhere else in our code

A knieve example:

Restangular.setErrorInterceptor(function(response, deferred, rejectCallbackDefined) {
  if (rejectCallbackDefined) {
    // Let the custom error handler do the work
    return true;
  }

  // Default error handling
  // ...
  return false;
}