vue2 'computed' value created after 'created' value











up vote
0
down vote

favorite












I am confused cause when I search google and find articles all tell me in vue's life cycle, 'computed' was before 'created',but in my code, i got result 2
before result 1, how can resolve this?



computed: {
options() {
const imgData = {
img: this.modifyData,
fixedNumber: this.ratio
}
console.log(1)
return Object.assign({}, this.defaultOptions, imgData)
}
},
watch: {
modifyData(nval) {
// nothing to do yet
}
},
created() {
console.log(2)
},
...




update:
'this.modifyData' was from axios.get(...) , so it would be undefined at the beginning, Though i have solved this problem but still confused why result 2 was go before result 1?










share|improve this question




















  • 2




    Can you link to these articles? Computed properties only execute during rendering and only when required by changes to reactive data
    – Phil
    Nov 22 at 2:10












  • I suggest you read this ~ vuejs.org/v2/guide/instance.html#Lifecycle-Diagram
    – Phil
    Nov 22 at 2:23















up vote
0
down vote

favorite












I am confused cause when I search google and find articles all tell me in vue's life cycle, 'computed' was before 'created',but in my code, i got result 2
before result 1, how can resolve this?



computed: {
options() {
const imgData = {
img: this.modifyData,
fixedNumber: this.ratio
}
console.log(1)
return Object.assign({}, this.defaultOptions, imgData)
}
},
watch: {
modifyData(nval) {
// nothing to do yet
}
},
created() {
console.log(2)
},
...




update:
'this.modifyData' was from axios.get(...) , so it would be undefined at the beginning, Though i have solved this problem but still confused why result 2 was go before result 1?










share|improve this question




















  • 2




    Can you link to these articles? Computed properties only execute during rendering and only when required by changes to reactive data
    – Phil
    Nov 22 at 2:10












  • I suggest you read this ~ vuejs.org/v2/guide/instance.html#Lifecycle-Diagram
    – Phil
    Nov 22 at 2:23













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am confused cause when I search google and find articles all tell me in vue's life cycle, 'computed' was before 'created',but in my code, i got result 2
before result 1, how can resolve this?



computed: {
options() {
const imgData = {
img: this.modifyData,
fixedNumber: this.ratio
}
console.log(1)
return Object.assign({}, this.defaultOptions, imgData)
}
},
watch: {
modifyData(nval) {
// nothing to do yet
}
},
created() {
console.log(2)
},
...




update:
'this.modifyData' was from axios.get(...) , so it would be undefined at the beginning, Though i have solved this problem but still confused why result 2 was go before result 1?










share|improve this question















I am confused cause when I search google and find articles all tell me in vue's life cycle, 'computed' was before 'created',but in my code, i got result 2
before result 1, how can resolve this?



computed: {
options() {
const imgData = {
img: this.modifyData,
fixedNumber: this.ratio
}
console.log(1)
return Object.assign({}, this.defaultOptions, imgData)
}
},
watch: {
modifyData(nval) {
// nothing to do yet
}
},
created() {
console.log(2)
},
...




update:
'this.modifyData' was from axios.get(...) , so it would be undefined at the beginning, Though i have solved this problem but still confused why result 2 was go before result 1?







vuejs2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 2:37

























asked Nov 22 at 2:07









Veexyy

83




83








  • 2




    Can you link to these articles? Computed properties only execute during rendering and only when required by changes to reactive data
    – Phil
    Nov 22 at 2:10












  • I suggest you read this ~ vuejs.org/v2/guide/instance.html#Lifecycle-Diagram
    – Phil
    Nov 22 at 2:23














  • 2




    Can you link to these articles? Computed properties only execute during rendering and only when required by changes to reactive data
    – Phil
    Nov 22 at 2:10












  • I suggest you read this ~ vuejs.org/v2/guide/instance.html#Lifecycle-Diagram
    – Phil
    Nov 22 at 2:23








2




2




Can you link to these articles? Computed properties only execute during rendering and only when required by changes to reactive data
– Phil
Nov 22 at 2:10






Can you link to these articles? Computed properties only execute during rendering and only when required by changes to reactive data
– Phil
Nov 22 at 2:10














I suggest you read this ~ vuejs.org/v2/guide/instance.html#Lifecycle-Diagram
– Phil
Nov 22 at 2:23




I suggest you read this ~ vuejs.org/v2/guide/instance.html#Lifecycle-Diagram
– Phil
Nov 22 at 2:23












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










When the vue instance is initialize, the created function is ran. That is why you see 2. The reason that the value from your computed property logs out 1 later is that computed properties are lazy, meaning that their values are not created until they are needed.






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',
    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%2f53422933%2fvue2-computed-value-created-after-created-value%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








    up vote
    0
    down vote



    accepted










    When the vue instance is initialize, the created function is ran. That is why you see 2. The reason that the value from your computed property logs out 1 later is that computed properties are lazy, meaning that their values are not created until they are needed.






    share|improve this answer

























      up vote
      0
      down vote



      accepted










      When the vue instance is initialize, the created function is ran. That is why you see 2. The reason that the value from your computed property logs out 1 later is that computed properties are lazy, meaning that their values are not created until they are needed.






      share|improve this answer























        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        When the vue instance is initialize, the created function is ran. That is why you see 2. The reason that the value from your computed property logs out 1 later is that computed properties are lazy, meaning that their values are not created until they are needed.






        share|improve this answer












        When the vue instance is initialize, the created function is ran. That is why you see 2. The reason that the value from your computed property logs out 1 later is that computed properties are lazy, meaning that their values are not created until they are needed.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 22 at 5:22









        Austio

        4,4871128




        4,4871128






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53422933%2fvue2-computed-value-created-after-created-value%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

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Calculate evaluation metrics using cross_val_predict sklearn

            Insert data from modal to MySQL (multiple modal on website)