azaleta

according to the current source (method [findUp] in fs.ts) when we passing FindUpOptions = {multiple: true} then we will check all files in the **[parent] path only** like: /project/myprj ->...

https://github.com/vueuse/vueuse/blob/main/packages/integrations/useAxios/index.ts#L171 add config to the execute should be ok

this is not same config, I think config should changed if your form.value is changed. (and also config can't automatic updated when you change form.) A ref here: https://github.com/vueuse/vueuse/issues/1347

As I said, config can't automatic updated when you change form There is no reactive here. UseAxios instance is created with config and then freeze. Only way to refresh this...

umm... `There is no reactive here.` -> This is not your problem.This is the design thing. `config` is not ref, so it will not be automaticly changed like reactive. (even...

> As I said, config can't automatic updated when you change form There is no reactive here. UseAxios instance is created with config and then freeze. > > Only way...

https://github.com/vueuse/vueuse/blob/main/packages/core/useFetch/index.ts#L392 https://github.com/vueuse/vueuse/blob/main/packages/integrations/useAxios/index.ts#L186 These 2 execute have different return type. Is it intended to design like this? @antfu Change execute func of useFetch should resolve this.

the problem is iframe is listening to point events I think you can avoid this by using css setting to get smooth move. But this will make scrolling of ifarme...

https://github.com/vueuse/vueuse/blob/main/packages/integrations/useAxios/index.ts#L41

 this is in template