deepClone | a simple , fast and harmless way to clone deeply | Functional Programming library

I have a class say ConstructionSet which is having name property having computed inside get method like as below

I have a Dictionary where I save objects to parse to my plugin system, some of these objects need to be a copy not the original so I use this DeepClone method:

I was recently looking over this question on deep cloning in C#: How do you do a deep copy of an object in .NET?

I'm not a C#/.NET expert, so if this is completely off, someone please correct me. Why aren't people suggesting doing the following?

I have an object that is a combination of literals and accessors:

I have a modal containing a button that fires a HTTP request, at which point the displayed html will change depending on a successful/error response from the server, where the response changes a state prop that is dealt with in the mapStatesToProps function.

The issue I have now is that I am wanting to reset the modal to its initial state pre-request when I close it. I had previously done this by using local component state but have since updated the functionality to use the request mapped state props shown above.

I am curious if it possible to reset the state without firing a dispatch to a random URI?

Component.jsx

To set this up I create 2 fleet objects, store them in an array, then print the array to console. This is what I get after both fleet objects are created.

We are using JobRunr to do some background job processing in Java.

We enqueue the jobs as follows:

I'm trying to change the Vuex state by splicing the state.todos array, changing the one Object in array with another One that is given in my component / through the mutations

this is my Vuex state

I am trying to implement a table in react where the user can edit individual rows by clicking the edit button on a row and then submit once he has made his change. I have say two components App.js and its child Table.js to implement this.

The way I thought of doing this initially was letting each of this component have their own state for rows and then the Table component reads from the props send to it by parent initially and only change the parent rows when users submits the change as oppose to onChange event. But I've read that reading props into state is an anti-pattern.

So decided to have everything in the parent by having two values for row (oldrows,newrows). And using them to maintain state instead, This is the design I came up with :

But what happens is whenever I click cancel the oldRows get bound to the newRows, here is a codePen example I put up:

https://codepen.io/snedden-gonsalves/pen/zYOVMWz