nested_form | Rails plugin to conveniently handle multiple models | Form library

As currently written, you don´t mutate your state in vuex, you mutate it outside of your store, which is the wrong way to do it. In this case, reactivity works from store to component, not the other way round.

In your case, to update your state with the new order, you simply do it like you maybe already doing in other mutations:

The link_to_add_association needs the form-object (f) from the parent (where the associations are defined). So at the nested level, you need to be aware of the parent-form-object.

Also: we would only want to render the Clone button if the record already exists. Maybe I should explain that better: the form and all Clone-partials are rendered on the server, and thus will not copy fields if they are edited/changed in the form. Is that clear? To be able to do that, we would need more javascript-code, and this might also be a very valid approach, maybe simpler: trigger the link_to_add_association link and in the cocoon:after-insert event we can prefill the fields copied from the to-be-cloned item, if there is one. But, as said, that would be a pure javascript solution.

To remain close to your initial suggestion, your views would look like (I did not copy the entire view)

So it turns out that everything was correct, except I completely missed this line:

Try updating your Gemfile to use json@1.8.2 instead of 1.8.1 - according to this thread Ruby 2.2.x is incompatible with json 1.8.1.

1.8.2 should be functionally similar and not affect any of your other dependencies.

You can also run bundle update json to let bundler try to fix it for you - but that may put you at a much later version than 1.8.2, I'm not sure.

No harm in trying a couple things and reverting your changes.

Use the data attribute.