Internally doesn't throw exception

[siscia]

Hi,

I lost a solid hour try to debuging a trivial problem.

Basically I was returrning a map with unique key was :resource I guess that such map was combined with the context and when liberator try to access a field like (-> ctx :resource :whatever) it blowed up because (ctx :resource) wasn't a map anymore.

It was weird because I couldn't get the exception, it just said "500 Internal Error" and didn't throw any exception.

Why Liberator didn't throw any exception ? It is the desired behaviour ?
If not how we can fix that ?

Greets

[andrewmcveigh]

Which version are you using? There was a regression in version 0.12.0 that caused this behaviour. For me it was fixed by 0.12.2.

[1] b119c9e

[siscia]

I use the last version, 0.12.2

It works perfectly if my code throw exception.

If I write a :post! and the function throw an exception it works as expected.

The problem is when is lberator itself at throw an exception.

Please see the pull request attached :)

[ordnungswidrig]

Thanks for the report and the PR. Could you please cleanup the PR, remove up-versioning etc?). would the test case be more precise if you'd remove the thrown exception in :exists?. As far as I understand you're point to the error triggered by altering :resource in :service-available?, right?

[siscia]

Hi,

Sorry, I explained extremely badly the problem.

It will take a while, but as soon as I get home (3 weeks) I will do my best to provide a better explanation and a more helpful pull request.

If anybody, in the meantime want to work on the problem is extremely welcome ;)