-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New components <Head>
and <Config>
#105
Comments
Does the |
It doesn’t: it’s only used for HTML
…On Wed 7. Aug 2024 at 17:26, Muhammad ***@***.***> wrote:
Does the <Head> component need to be hydrated?
—
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHVQRTINACGAROOLY5XFF3ZQI4BBAVCNFSM6AAAAABMESHATOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZTG4ZTQOJXGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
We can wrap it with solidjs's |
Neat, although it's the user who would nead to do the wrapping right? |
AFAIK, yes, and it’s a bit of a bummer |
Another workaround is using solidjs's <Show when={isServer}>
<Head>
<script
type="application/ld+json"
innerHTML={JSON.stringify({
"@context": "https://schema.org/",
contentUrl: { src },
creator: {
"@type": "Person",
name: author,
},
})}
></script>
</Head>
</Show> |
Indeed, but better than no solution at all though. |
I wonder if |
|
Although it doesn't seem to remove |
Let's see what Ryan says 👀 solidjs/solid#2248 (comment) |
Done: #105. |
Neat trick 💯 |
vike-solid
now has auseConfig()
component hook (see PR #102).The only thing missing to align with
vike-react
is to implement the<Config>
and<Head>
components.My failed attempt to implement it: #104.
Contribution welcome.
The text was updated successfully, but these errors were encountered: