Mixing
[Vue warn]: Avoid using non-primitive value as key, use string/number value instead
I'm building a clone of HackerNews and am getting the following error:
vue.esm.js?efeb:591 [Vue warn]: Avoid using non-primitive value as key, use string/number value instead.
found in
---> <Single> at src/components/Single.vue
<App> at src/App.vue
<Root>
The error seems to be coming from Single.vue but I can't work what it is? The template is as follows:
<template>
<div class="container">
<h2>{{ story.title }}</h2>
<p>Score: {{ story.score }}</p>
<p>{{ story.url }}</p>
<div v-for="comment in comments" :key="comment">
<div class="comment-wrap">
<div class="comment-block">
<p class="comment-text">{{ comment.text }}</p>
<div class="bottom-comment">
<div class="comment-author">{{ comment.by }}</div>
<div class="comment-date">{{ comment.time }}</div>
</div>
</div>
</div>
</div>
</div>
</template>
If anyone out there can help, that would be great!?
javascript vue.js
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
add a comment |
I'm building a clone of HackerNews and am getting the following error:
vue.esm.js?efeb:591 [Vue warn]: Avoid using non-primitive value as key, use string/number value instead.
found in
---> <Single> at src/components/Single.vue
<App> at src/App.vue
<Root>
The error seems to be coming from Single.vue but I can't work what it is? The template is as follows:
<template>
<div class="container">
<h2>{{ story.title }}</h2>
<p>Score: {{ story.score }}</p>
<p>{{ story.url }}</p>
<div v-for="comment in comments" :key="comment">
<div class="comment-wrap">
<div class="comment-block">
<p class="comment-text">{{ comment.text }}</p>
<div class="bottom-comment">
<div class="comment-author">{{ comment.by }}</div>
<div class="comment-date">{{ comment.time }}</div>
</div>
</div>
</div>
</div>
</div>
</template>
If anyone out there can help, that would be great!?
javascript vue.js
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
add a comment |
I'm building a clone of HackerNews and am getting the following error:
vue.esm.js?efeb:591 [Vue warn]: Avoid using non-primitive value as key, use string/number value instead.
found in
---> <Single> at src/components/Single.vue
<App> at src/App.vue
<Root>
The error seems to be coming from Single.vue but I can't work what it is? The template is as follows:
<template>
<div class="container">
<h2>{{ story.title }}</h2>
<p>Score: {{ story.score }}</p>
<p>{{ story.url }}</p>
<div v-for="comment in comments" :key="comment">
<div class="comment-wrap">
<div class="comment-block">
<p class="comment-text">{{ comment.text }}</p>
<div class="bottom-comment">
<div class="comment-author">{{ comment.by }}</div>
<div class="comment-date">{{ comment.time }}</div>
</div>
</div>
</div>
</div>
</div>
</template>
If anyone out there can help, that would be great!?
javascript vue.js
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
I'm building a clone of HackerNews and am getting the following error:
vue.esm.js?efeb:591 [Vue warn]: Avoid using non-primitive value as key, use string/number value instead.
found in
---> <Single> at src/components/Single.vue
<App> at src/App.vue
<Root>
The error seems to be coming from Single.vue but I can't work what it is? The template is as follows:
<template>
<div class="container">
<h2>{{ story.title }}</h2>
<p>Score: {{ story.score }}</p>
<p>{{ story.url }}</p>
<div v-for="comment in comments" :key="comment">
<div class="comment-wrap">
<div class="comment-block">
<p class="comment-text">{{ comment.text }}</p>
<div class="bottom-comment">
<div class="comment-author">{{ comment.by }}</div>
<div class="comment-date">{{ comment.time }}</div>
</div>
</div>
</div>
</div>
</div>
</template>
If anyone out there can help, that would be great!?
javascript vue.js
javascript vue.js
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
asked Nov 21 '18 at 20:33
jnowebjnoweb
3151411
3151411
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You can simply avoid the use of :key in your v-for.
...
<div v-for="comment in comments">
...
As vuejs documentation said:
It is recommended to provide a key with v-for whenever possible, unless the
iterated DOM content is simple, or you are intentionally relying on the
default behavior for performance gains.
answered Nov 21 '18 at 20:40
jotadejotade
613
add a comment |
The warning sources from <div v-for="comment in comments" :key="comment">, where the object comment is used as a key for v-for. The meaning of the warning is quite literal, don't use Object as key.
Use unique primitive value as key, maybe something like comment.id or ${comment.time}${comment.by}
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
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%2f53420082%2fvue-warn-avoid-using-non-primitive-value-as-key-use-string-number-value-inst%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
You can simply avoid the use of :key in your v-for.
...
<div v-for="comment in comments">
...
As vuejs documentation said:
It is recommended to provide a key with v-for whenever possible, unless the
iterated DOM content is simple, or you are intentionally relying on the
default behavior for performance gains.
answered Nov 21 '18 at 20:40
jotadejotade
613
add a comment |
You can simply avoid the use of :key in your v-for.
...
<div v-for="comment in comments">
...
As vuejs documentation said:
It is recommended to provide a key with v-for whenever possible, unless the
iterated DOM content is simple, or you are intentionally relying on the
default behavior for performance gains.
answered Nov 21 '18 at 20:40
jotadejotade
613
add a comment |
You can simply avoid the use of :key in your v-for.
...
<div v-for="comment in comments">
...
As vuejs documentation said:
It is recommended to provide a key with v-for whenever possible, unless the
iterated DOM content is simple, or you are intentionally relying on the
default behavior for performance gains.
answered Nov 21 '18 at 20:40
jotadejotade
613
You can simply avoid the use of :key in your v-for.
...
<div v-for="comment in comments">
...
As vuejs documentation said:
It is recommended to provide a key with v-for whenever possible, unless the
iterated DOM content is simple, or you are intentionally relying on the
default behavior for performance gains.
answered Nov 21 '18 at 20:40
jotadejotade
613
answered Nov 21 '18 at 20:40
jotadejotade
613
answered Nov 21 '18 at 20:40
jotadejotade
613
answered Nov 21 '18 at 20:40
jotadejotade
613
613
add a comment |
add a comment |
The warning sources from <div v-for="comment in comments" :key="comment">, where the object comment is used as a key for v-for. The meaning of the warning is quite literal, don't use Object as key.
Use unique primitive value as key, maybe something like comment.id or ${comment.time}${comment.by}
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
add a comment |
The warning sources from <div v-for="comment in comments" :key="comment">, where the object comment is used as a key for v-for. The meaning of the warning is quite literal, don't use Object as key.
Use unique primitive value as key, maybe something like comment.id or ${comment.time}${comment.by}
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
add a comment |
The warning sources from <div v-for="comment in comments" :key="comment">, where the object comment is used as a key for v-for. The meaning of the warning is quite literal, don't use Object as key.
Use unique primitive value as key, maybe something like comment.id or ${comment.time}${comment.by}
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
The warning sources from <div v-for="comment in comments" :key="comment">, where the object comment is used as a key for v-for. The meaning of the warning is quite literal, don't use Object as key.
Use unique primitive value as key, maybe something like comment.id or ${comment.time}${comment.by}
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
answered Nov 21 '18 at 20:37
William ChongWilliam Chong
919416
919416
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.
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%2f53420082%2fvue-warn-avoid-using-non-primitive-value-as-key-use-string-number-value-inst%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
