| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Hi and thanks for the PR! The team have been quite busy baking the upcoming NativeScript 5.0 release. We hope you love it as much as we do! The major release is the reason we taking longer with PR reviews. We will resume active reviewing in the following weeks. Thanks for your patience and for being awesome contributor! |
Sorry, something went wrong.
| return new Promise<http.HttpResponse>((resolve, reject) => { | ||
|
|
||
| if (!options.url) { | ||
| reject('Request url was empty.'); |
There was a problem hiding this comment.
Can you reject with an error (reject(new Error('Request url was empty.'));) to be consistent with the other reject path.
Sorry, something went wrong.
There was a problem hiding this comment.
Good call 👍 Updated now.
Sorry, something went wrong.
There was a problem hiding this comment.
Approve - once the comment is addressed.
Sorry, something went wrong.
|
test |
Sorry, something went wrong.
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Checklist
What is the current behavior?
Apps can error if url is invalid or response content is invalid.
What is the new behavior?
Error is properly caught and rejected to avoid Error: Uncaught (in promise) errors.