Promise Chaining and .then/.catch statementsHow does promise.all work?jQuery deferreds and promises - .then() vs .done()How do I convert an existing callback API to promises?Aren't promises just callbacks?What is the explicit promise construction antipattern and how do I avoid it?Handling multiple catches in promise chainHow do I tell if an object is a Promise?How do I access previous promise results in a .then() chain?Wait until all ES6 promises complete, even rejected promisesWhat is the difference between Promises and Observables?Catch in Promises

On a tidally locked planet, would time be quantized?

Longest common substring in linear time

Are the IPv6 address space and IPv4 address space completely disjoint?

What is this called? Old film camera viewer?

Drawing ramified coverings with tikz

If a character has darkvision, can they see through an area of nonmagical darkness filled with lightly obscuring gas?

Delivering sarcasm

What is Cash Advance APR?

Biological Blimps: Propulsion

Freedom of speech and where it applies

Travelling outside the UK without a passport

Is there a working SACD iso player for Ubuntu?

A social experiment. What is the worst that can happen?

Is it safe to use olive oil to clean the ear wax?

Why Shazam when there is already Superman?

How can Trident be so inexpensive? Will it orbit Triton or just do a (slow) flyby?

Is it possible to put a rectangle as background in the author section?

Closed-form expression for certain product

Why does the Sun have different day lengths, but not the gas giants?

Non-trope happy ending?

How to bake one texture for one mesh with multiple textures blender 2.8

Not using 's' for he/she/it

Electoral considerations aside, what are potential benefits, for the US, of policy changes proposed by the tweet recognizing Golan annexation?

Aragorn's "guise" in the Orthanc Stone



Promise Chaining and .then/.catch statements


How does promise.all work?jQuery deferreds and promises - .then() vs .done()How do I convert an existing callback API to promises?Aren't promises just callbacks?What is the explicit promise construction antipattern and how do I avoid it?Handling multiple catches in promise chainHow do I tell if an object is a Promise?How do I access previous promise results in a .then() chain?Wait until all ES6 promises complete, even rejected promisesWhat is the difference between Promises and Observables?Catch in Promises













1















The following code is taken from the last task of https://javascript.info/promise-api.



When I run the following, I am unable to get the output to match the alerts that the comments indicate. I assume that I am missing somethign with the catch statements, but I do not understand where I am going wrong. I appreciate any help!



// the whole promise chain fails with an error here
// change that:
// make errors appear as members of the results array

let urls = [
'https://api.github.com/users/iliakan',
// this URL is HTML page, it's invalid JSON, so response.json() fails
'/',
// this URL is invalid, so fetch fails
'http://no-such-url'
];

// Fix it:
Promise.all(urls.map(url => fetch(url).catch(err=>err)))
.then(responses => Promise.all(
responses.map(r => r.json().catch(err=>err))
))
// Demo output (no need to change):
.then(results =>
alert(results[0].name); // Ilya Kantor
alert(results[1]); // SyntaxError: Unexpected token < in JSON at position 0
alert(results[2]); // TypeError: failed to fetch (text may vary)
);











share|improve this question






















  • Possible duplicate of How does promise.all work?

    – Steven Stark
    Mar 8 at 4:54











  • are you getting any error?

    – binariedMe
    Mar 8 at 4:54











  • I am not getting any error, but no output is showing at all

    – Trebond
    Mar 8 at 6:52
















1















The following code is taken from the last task of https://javascript.info/promise-api.



When I run the following, I am unable to get the output to match the alerts that the comments indicate. I assume that I am missing somethign with the catch statements, but I do not understand where I am going wrong. I appreciate any help!



// the whole promise chain fails with an error here
// change that:
// make errors appear as members of the results array

let urls = [
'https://api.github.com/users/iliakan',
// this URL is HTML page, it's invalid JSON, so response.json() fails
'/',
// this URL is invalid, so fetch fails
'http://no-such-url'
];

// Fix it:
Promise.all(urls.map(url => fetch(url).catch(err=>err)))
.then(responses => Promise.all(
responses.map(r => r.json().catch(err=>err))
))
// Demo output (no need to change):
.then(results =>
alert(results[0].name); // Ilya Kantor
alert(results[1]); // SyntaxError: Unexpected token < in JSON at position 0
alert(results[2]); // TypeError: failed to fetch (text may vary)
);











share|improve this question






















  • Possible duplicate of How does promise.all work?

    – Steven Stark
    Mar 8 at 4:54











  • are you getting any error?

    – binariedMe
    Mar 8 at 4:54











  • I am not getting any error, but no output is showing at all

    – Trebond
    Mar 8 at 6:52














1












1








1








The following code is taken from the last task of https://javascript.info/promise-api.



When I run the following, I am unable to get the output to match the alerts that the comments indicate. I assume that I am missing somethign with the catch statements, but I do not understand where I am going wrong. I appreciate any help!



// the whole promise chain fails with an error here
// change that:
// make errors appear as members of the results array

let urls = [
'https://api.github.com/users/iliakan',
// this URL is HTML page, it's invalid JSON, so response.json() fails
'/',
// this URL is invalid, so fetch fails
'http://no-such-url'
];

// Fix it:
Promise.all(urls.map(url => fetch(url).catch(err=>err)))
.then(responses => Promise.all(
responses.map(r => r.json().catch(err=>err))
))
// Demo output (no need to change):
.then(results =>
alert(results[0].name); // Ilya Kantor
alert(results[1]); // SyntaxError: Unexpected token < in JSON at position 0
alert(results[2]); // TypeError: failed to fetch (text may vary)
);











share|improve this question














The following code is taken from the last task of https://javascript.info/promise-api.



When I run the following, I am unable to get the output to match the alerts that the comments indicate. I assume that I am missing somethign with the catch statements, but I do not understand where I am going wrong. I appreciate any help!



// the whole promise chain fails with an error here
// change that:
// make errors appear as members of the results array

let urls = [
'https://api.github.com/users/iliakan',
// this URL is HTML page, it's invalid JSON, so response.json() fails
'/',
// this URL is invalid, so fetch fails
'http://no-such-url'
];

// Fix it:
Promise.all(urls.map(url => fetch(url).catch(err=>err)))
.then(responses => Promise.all(
responses.map(r => r.json().catch(err=>err))
))
// Demo output (no need to change):
.then(results =>
alert(results[0].name); // Ilya Kantor
alert(results[1]); // SyntaxError: Unexpected token < in JSON at position 0
alert(results[2]); // TypeError: failed to fetch (text may vary)
);








javascript asynchronous promise es6-promise






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 8 at 4:45









TrebondTrebond

424




424












  • Possible duplicate of How does promise.all work?

    – Steven Stark
    Mar 8 at 4:54











  • are you getting any error?

    – binariedMe
    Mar 8 at 4:54











  • I am not getting any error, but no output is showing at all

    – Trebond
    Mar 8 at 6:52


















  • Possible duplicate of How does promise.all work?

    – Steven Stark
    Mar 8 at 4:54











  • are you getting any error?

    – binariedMe
    Mar 8 at 4:54











  • I am not getting any error, but no output is showing at all

    – Trebond
    Mar 8 at 6:52

















Possible duplicate of How does promise.all work?

– Steven Stark
Mar 8 at 4:54





Possible duplicate of How does promise.all work?

– Steven Stark
Mar 8 at 4:54













are you getting any error?

– binariedMe
Mar 8 at 4:54





are you getting any error?

– binariedMe
Mar 8 at 4:54













I am not getting any error, but no output is showing at all

– Trebond
Mar 8 at 6:52






I am not getting any error, but no output is showing at all

– Trebond
Mar 8 at 6:52













2 Answers
2






active

oldest

votes


















2














You do get an error from your code. In Firefox, for example, it will say TypeError: r.json is not a function in the developer console. (I see you're using alert() so you might not be familiar with the developer console and console.log() available in browsers. If this is so, I'd suggest looking in to them as the information they provide can be invaluable.)



The problem is that, in r.json(), r is either a response object or an exception object due to the earlier, first .catch(err=>err). Since exception objects do not have a json property, it throws its own exception. That exception isn't caught because there's no try/catch for it and .catch() is only useable on promises.



You could do something like this to check for and pass along an initial exception:



responses.map(r => r.json ? r.json().catch(err=>err) : r)





share|improve this answer

























  • That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

    – Trebond
    Mar 8 at 8:07


















0














The reason that this doesn't work is because in the first .catch(err=>err) statement, it is treating errors like a standard (successful) result. Then, any faulty data from fetch is called into the next Promise.all statement as it is treated as a good result, and thus r.json() will not know what to do with any faulty data (which is from fetch('/').






share|improve this answer






















    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55056875%2fpromise-chaining-and-then-catch-statements%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    You do get an error from your code. In Firefox, for example, it will say TypeError: r.json is not a function in the developer console. (I see you're using alert() so you might not be familiar with the developer console and console.log() available in browsers. If this is so, I'd suggest looking in to them as the information they provide can be invaluable.)



    The problem is that, in r.json(), r is either a response object or an exception object due to the earlier, first .catch(err=>err). Since exception objects do not have a json property, it throws its own exception. That exception isn't caught because there's no try/catch for it and .catch() is only useable on promises.



    You could do something like this to check for and pass along an initial exception:



    responses.map(r => r.json ? r.json().catch(err=>err) : r)





    share|improve this answer

























    • That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

      – Trebond
      Mar 8 at 8:07















    2














    You do get an error from your code. In Firefox, for example, it will say TypeError: r.json is not a function in the developer console. (I see you're using alert() so you might not be familiar with the developer console and console.log() available in browsers. If this is so, I'd suggest looking in to them as the information they provide can be invaluable.)



    The problem is that, in r.json(), r is either a response object or an exception object due to the earlier, first .catch(err=>err). Since exception objects do not have a json property, it throws its own exception. That exception isn't caught because there's no try/catch for it and .catch() is only useable on promises.



    You could do something like this to check for and pass along an initial exception:



    responses.map(r => r.json ? r.json().catch(err=>err) : r)





    share|improve this answer

























    • That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

      – Trebond
      Mar 8 at 8:07













    2












    2








    2







    You do get an error from your code. In Firefox, for example, it will say TypeError: r.json is not a function in the developer console. (I see you're using alert() so you might not be familiar with the developer console and console.log() available in browsers. If this is so, I'd suggest looking in to them as the information they provide can be invaluable.)



    The problem is that, in r.json(), r is either a response object or an exception object due to the earlier, first .catch(err=>err). Since exception objects do not have a json property, it throws its own exception. That exception isn't caught because there's no try/catch for it and .catch() is only useable on promises.



    You could do something like this to check for and pass along an initial exception:



    responses.map(r => r.json ? r.json().catch(err=>err) : r)





    share|improve this answer















    You do get an error from your code. In Firefox, for example, it will say TypeError: r.json is not a function in the developer console. (I see you're using alert() so you might not be familiar with the developer console and console.log() available in browsers. If this is so, I'd suggest looking in to them as the information they provide can be invaluable.)



    The problem is that, in r.json(), r is either a response object or an exception object due to the earlier, first .catch(err=>err). Since exception objects do not have a json property, it throws its own exception. That exception isn't caught because there's no try/catch for it and .catch() is only useable on promises.



    You could do something like this to check for and pass along an initial exception:



    responses.map(r => r.json ? r.json().catch(err=>err) : r)






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 8 at 8:09

























    answered Mar 8 at 7:40









    OuroborusOuroborus

    7,1861638




    7,1861638












    • That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

      – Trebond
      Mar 8 at 8:07

















    • That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

      – Trebond
      Mar 8 at 8:07
















    That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

    – Trebond
    Mar 8 at 8:07





    That makes sense, and thank you for clarifying my thoughts! I knew that it had something to do with the fact that the first .catch() statement treated exceptions like a regular object, but .json() would not know how to handle them. However, I was somewhat off the mark, because I was not sure what behavior it would exhibit exactly. Thank you for your insight @Ouroborus!

    – Trebond
    Mar 8 at 8:07













    0














    The reason that this doesn't work is because in the first .catch(err=>err) statement, it is treating errors like a standard (successful) result. Then, any faulty data from fetch is called into the next Promise.all statement as it is treated as a good result, and thus r.json() will not know what to do with any faulty data (which is from fetch('/').






    share|improve this answer



























      0














      The reason that this doesn't work is because in the first .catch(err=>err) statement, it is treating errors like a standard (successful) result. Then, any faulty data from fetch is called into the next Promise.all statement as it is treated as a good result, and thus r.json() will not know what to do with any faulty data (which is from fetch('/').






      share|improve this answer

























        0












        0








        0







        The reason that this doesn't work is because in the first .catch(err=>err) statement, it is treating errors like a standard (successful) result. Then, any faulty data from fetch is called into the next Promise.all statement as it is treated as a good result, and thus r.json() will not know what to do with any faulty data (which is from fetch('/').






        share|improve this answer













        The reason that this doesn't work is because in the first .catch(err=>err) statement, it is treating errors like a standard (successful) result. Then, any faulty data from fetch is called into the next Promise.all statement as it is treated as a good result, and thus r.json() will not know what to do with any faulty data (which is from fetch('/').







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 8 at 7:22









        TrebondTrebond

        424




        424



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55056875%2fpromise-chaining-and-then-catch-statements%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Identity Server 4 is not redirecting to Angular app after login2019 Community Moderator ElectionIdentity Server 4 and dockerIdentityserver implicit flow unauthorized_clientIdentityServer Hybrid Flow - Access Token is null after user successful loginIdentity Server to MVC client : Page Redirect After loginLogin with Steam OpenId(oidc-client-js)Identity Server 4+.NET Core 2.0 + IdentityIdentityServer4 post-login redirect not working in Edge browserCall to IdentityServer4 generates System.NullReferenceException: Object reference not set to an instance of an objectIdentityServer4 without HTTPS not workingHow to get Authorization code from identity server without login form

            2005 Ahvaz unrest Contents Background Causes Casualties Aftermath See also References Navigation menue"At Least 10 Are Killed by Bombs in Iran""Iran"Archived"Arab-Iranians in Iran to make April 15 'Day of Fury'"State of Mind, State of Order: Reactions to Ethnic Unrest in the Islamic Republic of Iran.10.1111/j.1754-9469.2008.00028.x"Iran hangs Arab separatists"Iran Overview from ArchivedConstitution of the Islamic Republic of Iran"Tehran puzzled by forged 'riots' letter""Iran and its minorities: Down in the second class""Iran: Handling Of Ahvaz Unrest Could End With Televised Confessions""Bombings Rock Iran Ahead of Election""Five die in Iran ethnic clashes""Iran: Need for restraint as anniversary of unrest in Khuzestan approaches"Archived"Iranian Sunni protesters killed in clashes with security forces"Archived

            Can't initialize raids on a new ASUS Prime B360M-A motherboard2019 Community Moderator ElectionSimilar to RAID config yet more like mirroring solution?Can't get motherboard serial numberWhy does the BIOS entry point start with a WBINVD instruction?UEFI performance Asus Maximus V Extreme