Next router: How to access multiple query parameters?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















OS: Windows 10 Pro

react: "^16.5.2"

next: "^7.0.2"

next-with-apollo: "^3.1.3"



So I'm having an issue with the query part of router.push whereby only the first defined query prop is detected but anything after is `undefined:






import Router from 'next/router';

Router.push({
pathname: '/order',
query: { id: order.data.createOrder.id, onToken: "true" },
});





In order I can access id by this.props.id but trying to access onToken via this.props.onToken reads as undefined.



What's the issue here?










share|improve this question























  • Shouldn't it be this.props.query.whatever?

    – Colin
    Nov 21 '18 at 23:40


















0















OS: Windows 10 Pro

react: "^16.5.2"

next: "^7.0.2"

next-with-apollo: "^3.1.3"



So I'm having an issue with the query part of router.push whereby only the first defined query prop is detected but anything after is `undefined:






import Router from 'next/router';

Router.push({
pathname: '/order',
query: { id: order.data.createOrder.id, onToken: "true" },
});





In order I can access id by this.props.id but trying to access onToken via this.props.onToken reads as undefined.



What's the issue here?










share|improve this question























  • Shouldn't it be this.props.query.whatever?

    – Colin
    Nov 21 '18 at 23:40














0












0








0








OS: Windows 10 Pro

react: "^16.5.2"

next: "^7.0.2"

next-with-apollo: "^3.1.3"



So I'm having an issue with the query part of router.push whereby only the first defined query prop is detected but anything after is `undefined:






import Router from 'next/router';

Router.push({
pathname: '/order',
query: { id: order.data.createOrder.id, onToken: "true" },
});





In order I can access id by this.props.id but trying to access onToken via this.props.onToken reads as undefined.



What's the issue here?










share|improve this question














OS: Windows 10 Pro

react: "^16.5.2"

next: "^7.0.2"

next-with-apollo: "^3.1.3"



So I'm having an issue with the query part of router.push whereby only the first defined query prop is detected but anything after is `undefined:






import Router from 'next/router';

Router.push({
pathname: '/order',
query: { id: order.data.createOrder.id, onToken: "true" },
});





In order I can access id by this.props.id but trying to access onToken via this.props.onToken reads as undefined.



What's the issue here?






import Router from 'next/router';

Router.push({
pathname: '/order',
query: { id: order.data.createOrder.id, onToken: "true" },
});





import Router from 'next/router';

Router.push({
pathname: '/order',
query: { id: order.data.createOrder.id, onToken: "true" },
});






reactjs next.js






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 23:17









TheoGTheoG

454826




454826













  • Shouldn't it be this.props.query.whatever?

    – Colin
    Nov 21 '18 at 23:40



















  • Shouldn't it be this.props.query.whatever?

    – Colin
    Nov 21 '18 at 23:40

















Shouldn't it be this.props.query.whatever?

– Colin
Nov 21 '18 at 23:40





Shouldn't it be this.props.query.whatever?

– Colin
Nov 21 '18 at 23:40












1 Answer
1






active

oldest

votes


















0














So I wrapped my component in withRouter() and accessed the individual parameters by calling this.props.router.query.






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%2f53421788%2fnext-router-how-to-access-multiple-query-parameters%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    So I wrapped my component in withRouter() and accessed the individual parameters by calling this.props.router.query.






    share|improve this answer




























      0














      So I wrapped my component in withRouter() and accessed the individual parameters by calling this.props.router.query.






      share|improve this answer


























        0












        0








        0







        So I wrapped my component in withRouter() and accessed the individual parameters by calling this.props.router.query.






        share|improve this answer













        So I wrapped my component in withRouter() and accessed the individual parameters by calling this.props.router.query.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 23:52









        TheoGTheoG

        454826




        454826
































            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%2f53421788%2fnext-router-how-to-access-multiple-query-parameters%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

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?