-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
text/template, html/template: document Funcs must be called before Parse #18971
Labels
Documentation
Issues describing a change to documentation.
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Comments
CL https://golang.org/cl/36425 mentions this issue. |
Just adding myself as a reviewer here; I'm not sure how to find the github account of the CL creator. |
Ping @gulyasm if am not mistaken. |
@paranoiacblack Yes, it's me. |
CL https://golang.org/cl/38413 mentions this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Documentation
Issues describing a change to documentation.
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Go 1.6+
What operating system and processor architecture are you using (
go env
)?Any
What did you do?
https://play.golang.org/p/SeHjhOvCFZ (html/template)
https://play.golang.org/p/EeVfv5_IcQ (text/template)
What did you expect to see?
I would expect that both
success()
andfail()
successfully write the string "foo" to stdoutWhat did you see instead?
The
fail
function panics with the error,panic: template: :1: function "foo" not defined
. If possible, it would feel much more consistent for both of these functions to succeed. If that is not possible, updating the documentation to reflect the need for custom functions to be defined before the template is loaded would be very helpful to confused users.See, for example:
The text was updated successfully, but these errors were encountered: