Vadim Vetrov comments

Results 7 comments of


                                            Vadim Vetrov

ref returned by toRefs(props) have type Ref<X | undefined> | undefined

> > `toRef()` works as expected. The prop is possibly undefined, so the generated ref possibly contains and `undefined` value: `Ref`. The propblem is only with `toRefs()` > I agree....

ref returned by toRefs(props) have type Ref<X | undefined> | undefined

> > But, I think, the main topic of this issue is that it is impossible to separate Ref from Ref > > If you have an optional prop (=...

ref returned by toRefs(props) have type Ref<X | undefined> | undefined

> > Did you check the reproduction? > > Your reproduction code is invalid, you are assigning `ref` to a `string`. > > The only valid point is the `Ref...

ref returned by toRefs(props) have type Ref<X | undefined> | undefined

Ok thank you

ref returned by toRefs(props) have type Ref<X | undefined> | undefined

> @pikax you sure? I think what OP tries to do here would require casting or a new ref. > > They are checking for .value to not be nullish,...

ref returned by toRefs(props) have type Ref<X | undefined> | undefined

Okey and thank you for your time

Resizing Wayland windows is either laggy or causes the application to freeze on GNOME + AMD

I am experiencing the same issue now. Arch linux, gnome(wayland) 46.1-2, glfw 3.4-2. Dual graphics laptop. Intel and Nvidia. When running on Intel card it just shutters and loads 100%...