Something noncompletely unreasonable like
"non" <> H.i "complete" <> "ly"
will give different results depending on which rendered is used:
-
Text.Blaze.Renderer.Text.renderMarkup gives
as intended.
-
Text.Blaze.Renderer.Pretty.renderMarkup gives
which will be shown in the browser as
non complete ly
A possible workaround is to encapsulate such content with H.unsafeLazyByteString . HR.renderHtml, but this doesn't feel safe nor elegant.
Something noncompletely unreasonable like
will give different results depending on which rendered is used:
Text.Blaze.Renderer.Text.renderMarkupgivesas intended.
Text.Blaze.Renderer.Pretty.renderMarkupgiveswhich will be shown in the browser as
A possible workaround is to encapsulate such content with
H.unsafeLazyByteString . HR.renderHtml, but this doesn't feel safe nor elegant.