Promise-based Wrapper for Simple HTTP Requests built on top of Bluebird and Request
If you choose to use
request-promise-native first you can later just replace it by request-promise without any breaking changes.
Of course not the other way around
dumb question: cookie jars passed into a function are passed by reference and not value?
@ProfessorTom Man, thatâs unfortunate! Regarding your question, yes by reference. Otherwise the last example at the very bottom of the
request README wouldnât work.
vueresource dependence promise
And the exception lock like about promise
I have no idea to resolve it
I think itâs best if you contact the
vue-resource community.
But I know vue resource is dependent on promise. And exception log tips about promise
@liaotup âpromiseâ doesnât mean ârequest-promiseâ. This chat is for the
request-promise library only. The vue.js community has a forum for your type of question: https://forum.vuejs.org Theyâll be able to help you.
hey @analog-nico FWIW, the problem I was having with cookies getting "updated" in cookieJars turned out to be a situation where I was using
request-promise but forgot to put a return in front of the call to request so the cookie was getting updated, but because I wasn't waiting on the promise to resolve, I had authentication errors.
experimenting previously, I wasn't able to get either
body or request out of awaiting a call to request. I don't know if I was just doing something wrong or if I really can't await request. Would be really cool if one could do this though. It would make testing code a lot cleaner
google it many times, thought it should work, but it doesn't , did i do anything wrong?
firsturl = 'someurl.json';
secondurl = 'some_second_url.json';
request = require('request-promise');
options = {
url: firsturl,
json: false,
header: "some_username_password"
}
request(options)
.then(function(data1) {
var data_first = JSON.parse(data1); //results from the first url
options.url = secondurl;
request(options)
.then(function(data2) {
var data_second = JSON.parse(data2);
console.log(data_second);
//why it prints the results from the first url???
})
})
I hate bugs like that
Unfortunately, I donât have time right now to look into it myself...
@ProfessorTom One idea you could try in your Typescript environment: Instead of using
await rp(âŚ) you could use await rp(âŚ).promise(). Since rp(âŚ) returns a mixed object that is a certain request object and a promise at the same time that may confuse the runtime. .promise() returns just the promise and that should definitely work with await.
I'm using your wonderful library in one of my projects and something weird keeps happening, is there anybody who could help me here or I should create an issue?
On my tests, sometimes req({option}).then() returns this error: "TypeError: req(...).then is not a function", I checked and on those cases req(...) is not a promise!
It's just my options (a json object )
It's just my options (a json object )
So what am I doing wrong? Couldn't find anything on your issues
Btw, you can also open an issue for that. Whatever you prefer.