-
Notifications
You must be signed in to change notification settings - Fork 838
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amended toService enabling the provision of a one-off httpConfig #1068
Conversation
This was a bug IMHO. All other restangular resources allow for providing a one-off httpConfig to be provided for a subsequent server request. I don't see a reasons why this shouldn't be allowed for .service created ones as well...
This PR is rather stale :) Could somebody at least comment on the issue? |
I can! I want this PR applied 👍 |
@mgonto Could you please merge this PR or comment on it? Thanks! |
Would you mind writing a test for this? |
Happy one year PR anniversary! I am not sure if @steinerj is still interested in this PR. However - I have an interest in getting this merged and I would volunteer if necessary. I have not contributed to restangular before, so I would need some guidance how to write a test. @steinerj asked for a "final spec" - @daviesgeek can you comment on this? |
@steinerj any comments? @madflow as far as unit tests go, take a look at the current tests. It should be relatively self-explanatory, but if you have any questions, read the Jasmine docs. If you still have questions, feel free to let me know :) |
@madflow Looks like you referenced this PR in your commit but didn't open a PR for your own branch? |
I wrote a first test - not sure if this will be "enough". Since this PR is stale - I opened a new one #1392 This PR can safely be closed I believe. |
Sorry guys, haven't been paying attention. Happy @madflow's PR is done and dusted! |
This was a bug IMHO. All other restangular resources allow for providing a one-off httpConfig to be used with a subsequent server request. There is no way, to provide a httpConfig for POST-requests issued by objects created with toService. I don't see a reason why this shouldn't be allowed for .service created ones as well...
This problem was also brought up in Issue #420
Tests pass. I'm happy to add a unit test, but I'm not sure if that's the "final spec" for objects created by toService.