kubaninc / scim_rails

02 Jun, 2020

1 commit

e05971b0 Merge pull request #27 from rreinhardt9/add-error-logging ... Browse Dir »
```
Add logging for unhandled exceptions
```
Kyle Werner
2020-06-02 13:15:52 -0500

29 May, 2020

1 commit

7ba7da5c Add ability to supply a callable error handler ... Browse Dir »

resolves lessonly/scim_rails#23

Why?
The scim engine returns a custom response to the caller in the event
that there is a 500 error in the engine. It rescues any standard error
in order to do this.

Unfortunately this means that when something is broken it does not
bubble up to the parent app's error handling system or even be printed
in the logs.

We cannot just re-raise the exception because you cannot return a
response AND raise an exception as a part of the same request.

To help, this PR will make is possible for you to supply a callable
object that take the exception as it's argument.

If no callable object is provided, we will output the exception to the
logs so that silence is not the default.

To get the old behavior of completely ignoring an exception, you could
supply an empty proc.

2020-05-29 17:39:19 -0400

09 Apr, 2019

1 commit

085e0aae Merge pull request #9 from lessonly/armilam/ch22217/loosen-rails-version-restriction-on-scim ... Browse Dir »
```
Update for use with Rails 5.2
```
WNjihia
2019-04-09 15:02:18 +0300

05 Apr, 2019

1 commit

b3df225f Remove second response content-type ... Browse Dir »

See https://github.com/lessonly/scim_rails/pull/9#issuecomment-480398815
for context. Having two content-type values for a response does not
make sense. And in fact, Okta's SCIM API reference says we should use
the application/scim+json response type.

This commit changes our uses of two content-type values to the one
that it should be.