Mixing
Vuejs Computed Property warns that I have no setter
I have a code like this:
<button
@click="addFieldRow"
:disabled="disableAddRow"
>
disableAddRow is a computed property like this:
disableAddRow() {
if (this.currentIndex !== null) {
return !this.fieldList[this.currentIndex].filterApplied;
}
if (this.currentIndex === null && this.fieldList.length === 1) {
return true;
}
return false;
}
Works as it should, but on my console log, I get the following warning:
[Vue warn]: Computed property "disableAddRow" was assigned to but it
has no setter.
I don't get why I need a setter? And if I do need a setter, I don't understand what I need to set...
Thank you for your time and help!
vuejs2 computed-properties
asked Nov 19 '18 at 17:36
LeesaLeesa
627
add a comment |
I have a code like this:
<button
@click="addFieldRow"
:disabled="disableAddRow"
>
disableAddRow is a computed property like this:
disableAddRow() {
if (this.currentIndex !== null) {
return !this.fieldList[this.currentIndex].filterApplied;
}
if (this.currentIndex === null && this.fieldList.length === 1) {
return true;
}
return false;
}
Works as it should, but on my console log, I get the following warning:
[Vue warn]: Computed property "disableAddRow" was assigned to but it
has no setter.
I don't get why I need a setter? And if I do need a setter, I don't understand what I need to set...
Thank you for your time and help!
vuejs2 computed-properties
asked Nov 19 '18 at 17:36
LeesaLeesa
627
1
That warning means that, somewhere in your code, you are assigning a value to yourdisableAddRowcomputed property. The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else.
– thanksd
Nov 19 '18 at 18:39
@thanksd Wow I am dumb. I was originally usingdisableAddRowas a non computed prop, I forgot I set a value else where. Could you add this as an answer, so I can mark it as answered? Thank you!
– Leesa
Nov 19 '18 at 18:50
add a comment |
I have a code like this:
<button
@click="addFieldRow"
:disabled="disableAddRow"
>
disableAddRow is a computed property like this:
disableAddRow() {
if (this.currentIndex !== null) {
return !this.fieldList[this.currentIndex].filterApplied;
}
if (this.currentIndex === null && this.fieldList.length === 1) {
return true;
}
return false;
}
Works as it should, but on my console log, I get the following warning:
[Vue warn]: Computed property "disableAddRow" was assigned to but it
has no setter.
I don't get why I need a setter? And if I do need a setter, I don't understand what I need to set...
Thank you for your time and help!
vuejs2 computed-properties
asked Nov 19 '18 at 17:36
LeesaLeesa
627
I have a code like this:
<button
@click="addFieldRow"
:disabled="disableAddRow"
>
disableAddRow is a computed property like this:
disableAddRow() {
if (this.currentIndex !== null) {
return !this.fieldList[this.currentIndex].filterApplied;
}
if (this.currentIndex === null && this.fieldList.length === 1) {
return true;
}
return false;
}
Works as it should, but on my console log, I get the following warning:
[Vue warn]: Computed property "disableAddRow" was assigned to but it
has no setter.
I don't get why I need a setter? And if I do need a setter, I don't understand what I need to set...
Thank you for your time and help!
vuejs2 computed-properties
vuejs2 computed-properties
asked Nov 19 '18 at 17:36
LeesaLeesa
627
asked Nov 19 '18 at 17:36
LeesaLeesa
627
asked Nov 19 '18 at 17:36
LeesaLeesa
627
asked Nov 19 '18 at 17:36
LeesaLeesa
627
asked Nov 19 '18 at 17:36
LeesaLeesa
627
627
1
That warning means that, somewhere in your code, you are assigning a value to yourdisableAddRowcomputed property. The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else.
– thanksd
Nov 19 '18 at 18:39
@thanksd Wow I am dumb. I was originally usingdisableAddRowas a non computed prop, I forgot I set a value else where. Could you add this as an answer, so I can mark it as answered? Thank you!
– Leesa
Nov 19 '18 at 18:50
add a comment |
1
That warning means that, somewhere in your code, you are assigning a value to yourdisableAddRowcomputed property. The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else.
– thanksd
Nov 19 '18 at 18:39
@thanksd Wow I am dumb. I was originally usingdisableAddRowas a non computed prop, I forgot I set a value else where. Could you add this as an answer, so I can mark it as answered? Thank you!
– Leesa
Nov 19 '18 at 18:50
1
1
That warning means that, somewhere in your code, you are assigning a value to your
disableAddRow computed property. The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else.– thanksd
Nov 19 '18 at 18:39
That warning means that, somewhere in your code, you are assigning a value to your
disableAddRow computed property. The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else.– thanksd
Nov 19 '18 at 18:39
@thanksd Wow I am dumb. I was originally using
disableAddRow as a non computed prop, I forgot I set a value else where. Could you add this as an answer, so I can mark it as answered? Thank you!– Leesa
Nov 19 '18 at 18:50
@thanksd Wow I am dumb. I was originally using
disableAddRow as a non computed prop, I forgot I set a value else where. Could you add this as an answer, so I can mark it as answered? Thank you!– Leesa
Nov 19 '18 at 18:50
add a comment |
1 Answer
1
active
oldest
votes
That warning is indicating that, somewhere in your code, you are assigning a value to your disableAddRow computed property.
The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else. You simply need to not set the value of the computed property and you won't get that warning anymore.
For a little more context: computed properties, by default, retrieve the value returned by the defining function. It is, however, possible to define setters for computed properties as well (which is what the warning is alluding to).
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
add a comment |
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
});
}
});
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%2f53379939%2fvuejs-computed-property-warns-that-i-have-no-setter%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
That warning is indicating that, somewhere in your code, you are assigning a value to your disableAddRow computed property.
The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else. You simply need to not set the value of the computed property and you won't get that warning anymore.
For a little more context: computed properties, by default, retrieve the value returned by the defining function. It is, however, possible to define setters for computed properties as well (which is what the warning is alluding to).
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
add a comment |
That warning is indicating that, somewhere in your code, you are assigning a value to your disableAddRow computed property.
The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else. You simply need to not set the value of the computed property and you won't get that warning anymore.
For a little more context: computed properties, by default, retrieve the value returned by the defining function. It is, however, possible to define setters for computed properties as well (which is what the warning is alluding to).
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
add a comment |
That warning is indicating that, somewhere in your code, you are assigning a value to your disableAddRow computed property.
The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else. You simply need to not set the value of the computed property and you won't get that warning anymore.
For a little more context: computed properties, by default, retrieve the value returned by the defining function. It is, however, possible to define setters for computed properties as well (which is what the warning is alluding to).
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
That warning is indicating that, somewhere in your code, you are assigning a value to your disableAddRow computed property.
The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else. You simply need to not set the value of the computed property and you won't get that warning anymore.
For a little more context: computed properties, by default, retrieve the value returned by the defining function. It is, however, possible to define setters for computed properties as well (which is what the warning is alluding to).
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
answered Nov 19 '18 at 19:09
thanksdthanksd
22.4k96273
22.4k96273
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%2f53379939%2fvuejs-computed-property-warns-that-i-have-no-setter%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
1
That warning means that, somewhere in your code, you are assigning a value to your
disableAddRowcomputed property. The code you shared wouldn't cause that warning, so you must be inadvertently assigning it a value somewhere else.– thanksd
Nov 19 '18 at 18:39
@thanksd Wow I am dumb. I was originally using
disableAddRowas a non computed prop, I forgot I set a value else where. Could you add this as an answer, so I can mark it as answered? Thank you!– Leesa
Nov 19 '18 at 18:50