Adrià Fontcuberta

Sure! I'll set up a minimal repro and see if the issue is still there – I wanted to make sure it wasn't an expected behavior

hey, thanks for the PR! > Great PR Although, I think the reason why it's structured the way it is, is to have all the Stacks/Technologies in one place and...

Have you tried passing `null` or empty values as optional parameter? Can't find where I used it but I recall doing it. Hope it helps.

Hi! Thanks for your message. Looks like you're right, I overlooked this bit: https://github.com/testing-library/vue-testing-library/pull/173/files#diff-25bf86bba97788343267cf1a217702b4825b65b411e7697b0daa7576a5eb79ecR23-R25 `instance-id` should be `1`. That being said: > I need to have a consistent API and...

Yep. I think we should: 1) Go back to the original behavior of setProps/rerender. 2) Find out if there's a way to keep the previous wrapper instance and update it,...

This is what React Testing Lib does: https://github.com/testing-library/react-testing-library/blob/master/src/pure.js#L81-L82 https://github.com/testing-library/react-testing-library/blob/master/src/__tests__/rerender.js they pass the whole component (with JSX)

(btw, I removed the `bug` label as now rerender what does it says on #176. However I leave the issue open to see if we find a better way to...

Thanks for getting back to this! I'll reread the whole thing to see what we can come up with 👍 However, re this >3. Again, looking at React Testing Library,...

Hi! 👋 as you mentioned in [the issue on testing-vue](https://github.com/storybookjs/testing-vue/issues/5), it looks like this is an upstream issue originated there?

Yeah, maybe we could improve something there… the reason to have a try/finally block is explained on this PR: https://github.com/testing-library/vue-testing-library/pull/142 if we can come up with a valid use case...