Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); GitHub - alexkappa/mustache: Mustache templating language in Go · GitHub
Skip to content

Repository files navigation

Mustache

Go ReferenceGo Build

This is an implementation of the mustache templating language in Go.

It is inspired by hoisie/mustache however it's not a fork, but rather a re-implementation with improved spec conformance, and a more flexible API (e.g. support for io.Writer and io.Reader).

It is built using lexing techniques described in the slides on lexical scanning in Go, and functional options as described in the blog post on self-referential functions and the design of options.

This package aims to cover 100% of the mustache specification tests, however, by the time of this writing, it is not complete.

For more information on mustache check the official documentation and the mustache spec.

Installation

Install with go get github.com/alexkappa/mustache.

Documentation

The API documentation is available at godoc.org.

Usage

The core of this package is the Template, and its Parse and Render functions.

template:=mustache.New()
template.Parse(strings.NewReader("Hello, {{subject}}!"))
template.Render(os.Stdout, map[string]string{"subject": "world"})

Helpers

There are additional Parse and Render helpers to deal with different kinds of input or output, such as string, []byte or io.Writer/io.Reader.

Parse(rio.Reader) errorParseString(sstring) errorParseBytes(b []byte) error
Render(wio.Writer, contextinterface{}) errorRenderString(contextinterface{}) (string, error)
RenderBytes(contextinterface{}) ([]byte, error)

Reader/Writer

f, err:=os.Open("template.mustache")
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to open file: %s\n", err)
}
t, err:=Parse(f)
iferr!=nil {
fmt.Fprintf(os.Stderr, "failed to parse template: %s\n", err)
}
t.Render(os.Stdout, nil)

Note: in the example above, we used Parse which wraps the t := New() and t.Parse() functions for conciseness.

String

t:=mustache.New()
err:=t.ParseString("Hello, {{subject}}!")
iferr!=nil {
// handle error
}
s, _:=t.RenderString(map[string]string{"subject": "world"})
iferr!=nil {
// handle error
}
fmt.Println(s)

Options

It is possible to define some options on the template, which will alter the way the template will parse, render or fail.

The options are:

  • Name(n string) Option sets the name of the template. This option is useful when using the template as a partial to another template.
  • Delimiters(start, end string) Option sets the start and end delimiters of the template.
  • Partial(p *Template) Option sets p as a partial to the template. It is important to set the name of p so that it may be looked up by the parent template.
  • SilentMiss(silent bool) Option sets missing variable lookup behavior.

Options can be defined either as arguments to New or using the Option function.

Partials

Partials are templates themselves and can be defined using the Partial option.

Note: It is important to name the partial using the Name option which should match the mustache partial tag {{>name}} in the parent template.

title:=New(
Name("header") // instantiate and name the templateDelimiters("|", "|")) // set the mustache delimiters to | instead of {{title.ParseString("|title|") // parse a template stringbody:=New()
body.Option(Name("body"))
body.ParseString("{{content}}")
template:=New(
SilentMiss(false), // return an error if a variable lookup failsPartial(title), // register a partialPartial(body)) // and another one...template.ParseString("{{>header}}\n{{>body}}")
context:=map[string]interface{}{
"title": "Mustache",
"content": "Logic less templates with Mustache!",
}
template.Render(os.Stdout, context)

Context

When rendering, context can be either a map or a struct. Following are some examples of valid context arguments.

ctx:=map[string]interface{}{
"foo": "Hello",
"bar": map[string]string{
"baz": "World",
}
}
mustache.Render("{{foo}} {{bar.baz}}", ctx) // Hello World
typeFoostruct { Barstring }
ctx:=&Foo{ Bar: "Hi, from a struct!" }
mustache.Render("{{Bar}}", ctx) // Hi, from a struct!
typeFoostruct { barstring }
func (f*Foo) Bar() string { returnf.bar }
ctx:=&Foo{"Hi, from a method!"}
mustache.Render("{{Bar}}", ctx) // Hi, from a method!
typeFoostruct { Barstring`tag:"bar"` }
ctx:=&Foo{ Bar: "Hi, from a struct tag!" }
mustache.Render("{{bar}}", ctx) // Hi, from a struct tag!

Tests

Run go test as usual. If you want to run the spec tests against this package, make sure you've checked out the specs submodule. Otherwise, spec tests will be skipped.

Currently, certain spec tests are skipped as they fail due to an issue with how standalone tags and empty lines are being handled. Inspecting them manually, one can see that the templates render correctly but with some additional \n which should have been omitted. See issue #1.

See SPEC.md for a breakdown of which spec tests pass and fail.

Contributing

If you would like to contribute, head on to the issues page for tasks that need help.

About

Mustache templating language in Go

Topics

Resources

Stars

74 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages