Add support for other http request types (POST/DELETE/PUT) about leonardo

[sagivf]

They should be supported. Why do you think otherwise?

[LiranBri]

so seems like there is a bug. i get:
Error: Unexpected request: POST http://localhost:8000/app/id1/audiences
No more request expected
at $httpBackend (angular-mocks.js:1244)
at proxy (leonardo.js:16)
at sendReq (angular.js:10558)
at serverRequest (angular.js:10268)
at processQueue (angular.js:14792)
at angular.js:14808
at Scope.$eval (angular.js:16052)
at Scope.$digest (angular.js:15870)
at Scope.scopePrototype.$digest (hint.js:1966)
at Scope.$apply (angular.js:16160)(anonymous function) @ angular.js:12520(anonymous function) @ angular.js:9292processQueue @ angular.js:14800(anonymous function) @ angular.js:14808Scope.$eval @ angular.js:16052Scope.$digest @ angular.js:15870scopePrototype.$digest @ hint.js:1966Scope.$apply @ angular.js:16160scopePrototype.$apply @ hint.js:2029(anonymous function) @ angular.js:23618n.event.dispatch @ jquery.js:4435r.handle @ jquery.js:4121
angular.js:12520 TypeError: Cannot read property 'method' of undefined
at responseError (leonardo.js:413)
at processQueue (angular.js:14792)
at angular.js:14808
at Scope.$eval (angular.js:16052)
at Scope.$digest (angular.js:15870)
at Scope.scopePrototype.$digest (hint.js:1966)
at Scope.$apply (angular.js:16160)
at Scope.scopePrototype.$apply (hint.js:2029)
at HTMLFormElement. (angular.js:23618)
at HTMLFormElement.n.event.dispatch (jquery.js:4435)

[sagivf]

do you have the same request url with a different verb (GET probably) -

it might be this issue #63

See if it works when you only have that url with POST) - you might need to clear the local storage from leonardo data.

[LiranBri]

you right. its probably the case.

btw,
i also encountered another bug- i added options of different response, choose them, but still always got the original response, no matter what i chose for the state.
i had to clear my localstorage and configure everything all over again to fix it

[sagivf]

Let's fix the first issue, it might help with other problems.
We'll be happy to know if there are still bugs after the next release.

Keep in my the the recording feature is relatively new and we've mostly been doing our configuration via code till now, so that is more safe and stable.

Thanks.
closing this in the mean time.

[sagivf]

@LiranBri In case you are interested - these issues should be fixed in 1.0.9. Would be glad to know other wise.

[LiranBri]

Hi @sagivf, it might sound stupid- but can you please edit my previous nickname from the last reply and change it to "LiranBri"? i'm trying to remove references of it from google for personal reasons

[sagivf]

done