fix: Support setProps runs computed and watcher when prop is object (#761)

[mya-ake]

Related: #761

Changes

• Changed to pass clones to props of createInstance in case of Object
• As a result of this change, test of mount.spec.js has been updated

[eddyerburgh]

Can you just use either the spread opertor (not sure if it will trigger reactivity on nested property objects), or lodash.merge, which we already use in setData.

[mya-ake]

OK, use lodash.merge.
(Using spread operators will no longer be instances of classes.)

[eddyerburgh]

I was looking at this fix and I'm not sure we should do it because it changes this behavior. Another solution I could think of was to throw an error and tell the user to call setProps with a new object

[mya-ake]

I confirmed the processing of Vue.js, but it was the same value. So, I thought it would be better not to use deep.

Another solution I could think of was to throw an error and tell the user to call setProps with a new object.

I think that is a good way. But I want to use the same object.
I'll look into a way to fix again.

[mya-ake]

@eddyerburgh

Changes

• To clone data when it is an object.
• It does not affect other tests

[eddyerburgh]

This is a good solution, but it still suffers from this problem:

it('setProps removes reference', () => {
  const TestComponent = {
    template: `<div val="value"></div>`,
    props: ['value']
  }
  const wrapper = mountingMethod(TestComponent)
  const value = {}
  wrapper.setProps({value})
  expect(wrapper.props().value).to.equal(value)
})

I think a better solution would be to throw an error if the object in setProps has the same reference, and make the user create a new object. That way we situations that might be confusing, like the above.

[mya-ake]

Hmmm, I can't think of a way to pass the test.
I will withdraw this Pull request and the next Pull request will throw an error when the same reference.