You are ignoring the past, future and features of GOLANG HTML when you say
HTML comments are removed as a default. I'm guessing the original design
transmitted HTML comments and they just suppressed them. At some point, I'm
guessing they will add a GOLANG HTML template switch that transmits HTML
co
On Wednesday, 1 January 2025 at 21:44:25 UTC Mike Schinkel wrote:
If it stripped HTML comments then it would not be possible to generate
output that contains wanted comments.
But it *does* strip comments, doesn't it?
https://go.dev/play/p/0EChuy5CjyH
--
You received this message because you a
If it stripped HTML comments then it would not be possible to generate output
that contains wanted comments. Not all generated code is destined to be
delivered to a renderer. Some might be targeting developers who need to modify
it manually and for whom comments would be desired, i
More to the point, why is atilkan coding `` an HTML comment when golang templates is
a preprocessor language.that is going to strip HTML comments? If he is
retaining code in the template for future reference, then why not use a
template comment {{ /* */ }} instead of an HTML comment. Anyone familia
Yep that would fix the issue. But i am thinking those stripped html
comments should not be evaluated. That seems odd to me.
On Tuesday, 31 December 2024 at 11:20:37 UTC+3 Kurtis Rader wrote:
> Argh! I just realized my reference to the comment about the html/template
> "HTML" type handling of c
Argh! I just realized my reference to the comment about the html/template
"HTML" type handling of comments isn't really relevant. The issue is that
the html/template package doesn't inhibit substitution inside a semantic
HTML comment. It does elide comments from the generated output but does
attemp
Sorry, I was thinking you were talking about the html template tags. HTML
comments are processed like any other html tag. Does one of the
following produce the results you are looking for:
{{ `` }}
{{ /* `` */ }}
On Mon, Dec 30, 2024 at 10:34 PM Emrah ATILKAN
wrote:
> I don’t think it is J
You should always include the full error message (and backtrace if
available) as well as telling us the relevant version of Go you used to
compile your program and the particular package you believe is the source
of the problem. A minimal reproducible example is also a good idea if
feasible.
In th
I don’t think it is JS error. This is a Go runtime error. Not from browser
console, from terminal.
On Tue, Dec 31, 2024 at 02:33 Jon Perryman wrote:
> *"can't evaluate field nonExistingData"* looks like a javascript error
> message because it says evaluated. HTML would not evaluate stuff. The o
*"can't evaluate field nonExistingData"* looks like a javascript error
message because it says evaluated. HTML would not evaluate stuff. The outer
tics also make me think javascript. I inserted the statement (with &
without outer tics) but don't get an error message on the console.
On Mon, Dec 30,
Hi,
I am trying to add html comment (yes, they will be removed). I believe it
strips the comments after processing the template. If you put non-existing
property inside html comments, it throws error.
Maybe better to strip comments before processing the template?
``
I would paste the whole err
11 matches
Mail list logo
