vue.js - Why Data gets leaked into sibling Instance of Component when Removed vue 2 -


i building following scenario. parent creates multi instances of child component. each child holds data via input field. child can ask removed , parent removes instance. far good. problem, instance removed, data gets passed/leaked next sibling instance , if instance holding data, gets moved other next-to-it instance. have reproduced on fiddle

or see below 

    vue.component('child', {      	props:['data'],          template: `              <div>                  index# {{data}}: {{messages}}                  <input type="text" v-model="text" @keypress.enter="addmessage" placeholder="add data delete it">                  <button @click="addmessage">add</button>                  <button @click="$emit('delete-me')">delete</button>              </div>`,              data() {              	return {                	messages:[],                  text: ''                }              },              methods: {              	addmessage() {                	this.messages.push(this.text)                  this.text = ''                }              }      })            vue.component('parent', {          template: `              <div>                  keep adding new instances                   <button @click="newchild">new</button>                  <hr />                  <child v-for="(child, index) in children" key="index"                  v-on:delete-me="deletethisrow(index)""                  :data="child"                  ></child>              </div>`,              data() {              	return {                	children:[]                }          },          methods: {          	newchild() {            	this.children.push(this.children.length)            },            deletethisrow(index) {                  this.children.splice(index, 1);              }          }      })            new vue({          el: '#app',          template: `              <div>              		<parent />                                </div>          `,                    methods: {                        }      })                
<script src="https://cdnjs.cloudflare.com/ajax/libs/vue/2.3.3/vue.min.js"></script>  <div id="app"></div>

two mistakes in here:

  1. :key instead of key

reason: since dynamic values can change, vue should know change keep updated

  1. child instead of index

reason: not sure may because vue holds own copy of indices in virtual dom needs values only


Comments

Post a Comment

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

python Tkinter Capturing keyboard events save as one single string -

is possible store keyboard events 1 string? code below stores 1 char , prints it. card reader or bar code reader, contains collection of character/ string not 1 character @ time. goal save char pressed text variable. from tkinter import * root = tk() def key(event): text= event.char text+= event.char print ("pressed", text) def callback(event): frame.focus_set() print ("clicked at", event.x, event.y) frame = frame(root, width=100, height=100) frame.bind("<key>", key) frame.bind("<button-1>", callback) frame.pack() root.mainloop() currently, creating text variable , everytime key() function gets called, , text stores last character typed. you can define text module level variable , , use module level text inside key function - text = '' def key(event): global text text+= event.char print("pressed", text)
Read more

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -

here tables: create table customer ( cid int primary key, name varchar(32) ) create table ord ( oid int primary key, cid int foreign key references customer, address varchar(20) ) here's linq-to-sql statement: var aaa = c in db.customer select new { c, o = c.ord.tolist() }; and here's inexplicable query generated linq-to-sql: select [t0].[cid] [cid], [t0].[name] [name], [t1].[oid] [oid], [t1].[cid] [cid2], [t1].[address] [address], (select count(*) [dbo].[ord] [t2] [t2].[cid] = [t0].[cid]) [value] [dbo].[customer] [t0] left outer join [dbo].[ord] [t1] on [t1].[cid] = [t0].[cid] order [t0].[cid], [t1].[oid] i want understand how rid of count(*) part. it's entirely uncalled for! linq needs count(*) in order determine number of entries returned o = c.ord.tolist() .
Read more