Skip to main content

What is the implementation and difference between js deep copy and shallow copy?

 Deep copy is to re-open a new reference address for the variable, which is completely separated from the original, which is equivalent to dividing a new space for itself. Although the content in it is the same, even if one of them is changed, the other is not. will be affected. Shallow copy means that the reference address of the reference type in the stack cannot be changed. The two variables share the same reference address and change the things in the same place. Therefore, the shallow copy causes the change of one variable to cause the same change of the other variable. .

Deep copy of objects using parsing structures in es6

 let obj1={id:100,name:"aaa"};
    let obj2={...obj1};
    obj2.name="bbb";
    console.log(obj1);//{id: 100, name: "aaa"}
    console.log(obj2);//{id: 100, name: "bbb"}
Deep copy using methods in JSON
let obj1={id:100,name:"aaa"};
    let obj2=JSON.parse(JSON.stringify(obj1));
    obj2.name="bbb";
    console.log(obj1);//{id: 100, name: "aaa"}
    console.log(obj2);//{id: 100, name: "bbb"}
    </script>
Deep copy using recursion
let obj2={};
    function deepCopy(newObj,oldObj){
        for(let item in oldObj){
            if(oldObj[item] instanceof Object){
                newObj[item]={};
                deepCopy(newObj[item],oldObj[item]);
            }
            else if(oldObj[item] instanceof Array){
                newObj[item]=[];
                deepCopy(newObj[item],oldObj[item]);
            }
            else{
                newObj[item]=oldObj[item];
            }
        }
    }
    deepCopy(obj2,obj1);
    obj2.hobby.two="hello";
    console.log(obj1);
    console.log(obj2);


Comments

Popular posts from this blog

Using ref to bind elements in Vue

 Vue provides us with a property to manipulate dom, ref. When bound to the dom element, it is used similar to the id. It is called through this.$refs, and it can also be bound to the component. It is very troublesome to obtain DOM elements in the previous native way. It needs to be obtained with such a long AP as: documentgetElementXXX/querySXXX.... Then jQuery was born to solve this pain point. The use of $("id") makes Our operation has become easier. But there are other problems, jQuery is just a library (plug-in) and cannot be used to build a framework. Now Vue can help us solve this problem. Vue also has its own method to obtain DOM, which is ref. It can get not only DOM elements but also components. If you add ref to the dom element, you can get the dom element, and if you add it to the component, you can get the component instance, and you can use the component method.

Use of custom events in Vue components.

 The parent component uses props to pass data (such as a method) to the child component, and the child component needs to use custom events to pass data back to the parent component! We can use v-on to bind custom events, and then pass them to subcomponents, which will call after receiving the method. Each Vue instance implements the Events interface, that is: use $on(eventName) to listen for events and $emit(eventName) to trigger events.

mapState, mapGetters, mapMutations, mapActions in vuex

 The above four objects are all in the vuex plug-in store, which is often used to store some data shared globally. But I still feel a little uncomfortable when using it, that is, I wrote a lot of repeated prefixes. At this time, these four objects appeared, which solved this pain point very well. mapState is mainly used to manipulate and obtain data, mapGetters is equivalent to computed properties, and mapMutations and mapActions are simplifications of mutation and action. They can be written as both objects and arrays.