Matej Černý

I've updated the code to support dot notation for the `value-attribute` prop in ``. I also wanted to add dot notation support for the `by` prop, but ran into a...

Could you please share an example of a case where something fails to resolve, but we wouldn’t want to throw an error here? 🙏 I'd like to test it. The...

I've revisited this issue and noticed that since the modules are installed after the `ComposableKeysPlugin`, it doesn't appear possible to add new `keyedComposables` from modules. Could we address this by...

I was thinking about adding something similar to the config object. 👍 We should also consider the scenario where a module adds an entry to `keyedComposables` and the user wants...

Yes, it does. You can add a regex to it as well. Basically the import must either match the string you provide to `source` exactly, or the provided regex. I've...

I think you can go ahead 👍🙂 Though it might make module authors look through the source code and discover the undocumented `source` configuration option once they see the added...

I am a bit confused about whether this issue concerns a custom `$fetch` instance, which should already work fine with `$fetch.create`, or a custom `useFetch`, in which case it will...

@maximepvrt that is already possible in using `$fetch.create(/* defaults */)` - or am I missing something? https://nuxt.com/docs/guide/recipes/custom-usefetch#custom-fetch

You can already register the custom `$fetch` instance to be auto-imported too. Either by putting it inside the `utils` folder, or by configuring the auto-import manually. ```ts // utils/myFetch.ts export...

I think that this should be configured on a per-link basis rather than for the entire app because of @Ragura 's good point. Maybe as a NuxtLink prop?