Vuex would throw warnings about modules getting overridden if I call render() in more than one test

[davidchai717]

Oddly this doesn't have if you only have one test that calls render(component, { state: { foo: true }, modules: {...} }). But once I start adding in a second test where I need to render the same component with a Vuex store, it immediately starts throwing these module warnings.

I'd definitely appreciate some assistance here.

[afontcu]

Hi! Sorry this slipped through the cracks. Do you still experience this issue?

Could you share a snippet/codesandbox/repo where the issue could be reproduced? That'd help a lot.

I'd suggest making sure you're not sharing the component instance between tests.

Cheers! 👋

[ITenthusiasm]

@davidchai717 Is the example code you provided (render(component, { state: { foo: true }, modules: {...} })) literally what's in your code base right now? If it is, you're missing the store property in the object scheme. It would be easier if you wrote something like

const store = { state: { foo: true }, modules: {...} };
render(component, { store });

But if that isn't your issue then as afontcu said, a code snippet would be really helpful in getting to the bottom of this.

[afontcu]

Closing as we fixed the issue in Discord :) Turns out lodash' merge mutates original source, so the store object was leaking between tests.

[lukashambsch]

@afontcu What commit fixed this? Has it been released already? I'm seeing the same issue on 5.6.2 right now.

[afontcu]

The fix was to avoid mutating the original store when using lodash merge, and create a new object instead. No fix in VTL was needed 😉

[lukashambsch]

The fix was to avoid mutating the original store when using lodash merge, and create a new object instead. No fix in VTL was needed 😉

Ahh, I see. Thanks!