Closed shahyar closed 1 month ago
It's best if extensions are all-or-nothing, for many reasons.
Maybe we can make vike-react more configurable to fit your use case. What is it you're trying to achieve?
Fair enough! I was hoping to control the output of the base HTML in this case. Such as changing attributes on the and
tags. But I can do without it by adding another element into the body, I suppose.I add tailwind classes, and also data attributes during navigation.
The plan is to add settings to vike-react to accommodate your needs.
Would bodyAttributes: Record<string, string>
and htmlAttributes: Record<string, string>
work for you?
That works!
Would
bodyAttributes: Record<string, string>
andhtmlAttributes: Record<string, string>
work for you?
Done.
In the event someone wants to create their own
onRenderHtml
HTML output, but still wants to take advantage of the other featuresvike-react
provides, we should exportgetHeadHtml
andgetPageHtml
.Although, maybe the best way to do this is to have yet another hook which returns the HTML.