Rethinking Html Rendering, a la SSR #235
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is in response to issue #231, which calls for a nicer way to declare the doctype.
The old way of rendering HTML directly, which is to say not via the virtual dom, for the purposes of SSR or another JVM html use case, was to do something like this:
Mostly ok, kinda, except that
includeDocType
is just a boolean, and I was quite taken by ScalaTags approach of just letting you prefix a string so that the doctype could be whatever you wanted.So I took out
includeDocType
, and while wondering what do do next, I organised therender
extensions methods, then I realised that asking someone to supply theview
and themodel
, just so that I could callview(model).render
for them in a clunky way viaTyrianSSR.render
was daft.So now you just do any of these, and you're done:
What about the doctype?! Well... it's just a string you prefix to your rendered HTML. Do you need me for that? 🤔
I have provided a constant for the default...