[🐞] Weird behavior when accessing props value in differents way about qwik

[wmertens]

can you explain exactly what errors you're getting? Also, try updating qwik-ui

[Wykks]

If you open the modal then close it (click or esc key), there's this error (and then the app doesn't work anymore) :

props.stuff is undefined MyStuffModalContent_component_fooSig_useComputed_sBXmoQdQVq

stuff is set to undefined like this :

onClose$={() => {
    stuffSig.value = undefined;
}

But this should not happen, because the modal component should be destroyed before being updated.

The weird part is that when reading stuff like this :

const foo = props.stuff.foo;
return <div>{foo.foo2}</div>;

It doesn't work (props.stuff is undefined on modal close).

But this doesn't throw any errors :

const stuff = props.stuff;
return <div>{stuff.foo.foo2}</div>;

Also the first case const foo = props.stuff.foo; works if directly written in the main modal component.

This is a very short repro, it doesn't seems a big deal, bug with more code and more complicated models this can be hard to debug (at least for me, as I'm still not used to debug Qwik... quickly 😅 )

(Also qwik-ui updated, no changes)

[Wykks]

@PatrickJS Can you elaborate a bit why this is "not planned" ? 😅
I believe this is a important issue in Qwik. Quite easy to workaround, but not that easy to debug. I spent hours to identify the bug and make that reproduction, I could have spend more hours to narrow it more but closing this like that is not motivating...