fix: useSeoMeta type

[nWacky]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Currently useSeoMeta accepts UseSeoMetaInput type

UseSeoMetaInput can be both `T` and `() => T`

type UseSeoMetaInput = MaybeComputedRefEntries<MetaFlatInput> & {
  title?: ReactiveHead["title"];
  titleTemplate?: ReactiveHead["titleTemplate"];
};

type MaybeComputedRefEntries<T> =
  | MaybeComputedRef<T>
  | {
      [key in keyof T]?: MaybeComputedRefOrPromise<T[key]>;
    };

type MaybeComputedRef<T> = T | MaybeReadonlyRef<T> | Ref<T>;

type MaybeReadonlyRef<T> = (() => T) | ComputedRef<T>;

Because of this, typescript thinks both examples below are valid:

// computed that returns MetaFlatInput
useSeoMeta(() => {
  console.log("seo meta called");

  return {
    description: "description",
  };
});



const description = computed(() => {
  console.log("seo meta called");

  return "description";
});

// MetaFlatInput with computed properties
useSeoMeta({
  description,
});

After 1.8 computed that returns MetaFlatInput no longer works

Update UseSeoMetaInput type to reflect that

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.
  current documentation is up to date

[harlan-zw]

Thanks :) Sorry for the delay