Schema types break under certain conditions
See original GitHub issuethis may be a https://github.com/harlan-zw/zhead issue…
Here are some things that should be typed properly:
useHead({
link: [{ rel: 'mask-icon', href: '/safari-pinned-tab.svg', color: '#1a202c' }] // color is not allowed
})
useHead({
link: [
...[].map(() => ({ rel: 'prefetch', href: '' })), // this damages the type inference
{ rel: 'icon', type: 'image/svg', href: '/favicon.svg' },
]
})
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Breaking Unhealthy Patterns: Part II - Schemas
People develop ways to avoid triggering schemas in order not to feel the pain they come with. There are three types of schema...
Read more >Schema checks - Apollo GraphQL Docs
Types of schema changes. Not every change to a schema is a potentially breaking change. Additive changes (such as adding a field to...
Read more >Schema Evolution and Compatibility - Confluent Documentation
The following table presents a summary of the types of schema changes allowed for the different compatibility types, for a given subject. The...
Read more >Structuring a complex schema — Understanding JSON ...
Like any other code, schemas are easier to maintain if they can be broken down into logical units that reference each other as...
Read more >What is a schema? - TechTarget
A schema in computer programming is the structure for a database. It is also the formal expression of an inference rule for artificial...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, interesting. This may be an issue with the Nuxt types in that case.
The way that the Schema is typed in v1 is much simpler now which should resolve the issue.
Going to close off for now, if you spot the issue again please let me know 😃