fix for @vueuse/head doesn't function properly with ionic

[chibx]

I created an utility function, useIonHead, that works almost the same as useHead from unhead, but just with a hack around. The function provides a way to dispose and patch the created head object just like useHead. During the process, I realized that tabbed view was a big problem when trying to create this util, and the randomness of the Ionic Hooks. The main issue was leaving from a tabbed view to a non-tabbed view and trying to mantain or destroy state. Guess What: You can nest useIonHead calls within children components and still retain the same structure after the page it was created on, is brought into view, and it's also fast as well.

[netlify[bot]]

✅ Deploy Preview for friendly-lamington-fb5690 canceled.

Name	Link
🔨 Latest commit	e2890a4e29b7781c82303ee2ab83250a62f7243b
🔍 Latest deploy log	https://app.netlify.com/sites/friendly-lamington-fb5690/deploys/65d6a0500efa7c00073099b3

[danielroe]

This is fantastic! Do you think we should overwrite useHead instead of creating an additional composable?

[chibx]

This is fantastic! Do you think we should overwrite useHead instead of creating an additional composable?

@danielroe Sure, I guess changing the name to useHead would be better for ease when working with ongoing projects