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?
vuejs2
add a comment |
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?
vuejs2
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
add a comment |
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?
vuejs2
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
vuejs2
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
add a comment |
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
add a comment |
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.
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Nov 22 at 5:22
Austio
4,4871128
4,4871128
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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