29 May, 2020

1 commit

  • 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.
    Ross Reinhardt
     

16 Mar, 2020

1 commit


15 Mar, 2020

1 commit


19 Nov, 2019

5 commits


02 Oct, 2019

1 commit


20 Sep, 2019

3 commits


19 Sep, 2019

2 commits


09 Apr, 2019

1 commit


05 Apr, 2019

1 commit

  • We've expanded Rails version support up to 5.x.x.
    We have also changed the response Content-Type.
    
    And we plan to release a version after this PR is merged.
    Aaron Milam
     

13 Feb, 2019

2 commits


30 Jan, 2019

1 commit


29 Jan, 2019

2 commits


17 Jan, 2019

1 commit


14 Jan, 2019

1 commit


20 Dec, 2018

1 commit


11 Dec, 2018

3 commits


05 Dec, 2018

3 commits


20 Nov, 2018

2 commits


05 Nov, 2018

3 commits