A Go templating engine inspired by Leaf
Go to file
Elara bb9b6c8128 Add NilToZero option 2024-03-20 14:31:43 -07:00
.github Add FUNDING.yml 2023-12-16 00:14:31 +00:00
assets/icons Add logo svg to repo 2023-11-03 16:57:41 -07:00
ast Add support for maps and arrays 2024-03-07 14:06:59 -08:00
examples Add the ability to ignore errors in ExprTags 2024-02-07 18:27:21 -08:00
parser Run generator 2024-03-12 20:33:03 -07:00
.gitignore Add recursion example 2023-10-31 14:05:21 -07:00
LICENSE Switch to MPL-2.0 to allow static linking 2023-12-18 09:16:33 -08:00
README.md Add a few new default functions 2024-02-27 21:43:35 -08:00
expr.go Return an error if we encounter an unknown operator 2023-12-22 15:45:28 -08:00
expr_test.go Add more tests 2024-02-11 19:04:07 -08:00
for_tag.go Add index to map iteration 2024-02-20 12:07:39 -08:00
fs_tag.go Rename static_tag.go to fs_tag.go 2024-02-28 19:10:56 -08:00
func_test.go Add TestValidateFunc 2024-02-12 11:05:19 -08:00
go.mod Move ast and parser out of internal 2023-10-30 18:38:53 -07:00
if_tag.go Fix else/elif tags for nested if statements 2023-12-22 19:15:56 -08:00
include_tag.go Add the ability to ignore missing macros/templates in macro and include tags 2024-02-20 12:10:23 -08:00
macro_tag.go Add the ability to ignore missing macros/templates in macro and include tags 2024-02-20 12:10:23 -08:00
namespace.go Add NilToZero option 2024-03-20 14:31:43 -07:00
parse.go Add WriteOnSuccess option 2023-12-28 07:19:58 -08:00
salix.go Add NilToZero option 2024-03-20 14:31:43 -07:00
structs_test.go Add tests for negative indices 2024-02-23 22:15:43 -08:00
tag_test.go Add some tests 2023-11-03 23:36:41 -07:00
tags.go Switch to MPL-2.0 to allow static linking 2023-12-18 09:16:33 -08:00
test_utils.go Add more tests 2024-02-11 19:04:07 -08:00
vars.go Don't escape JSON data as HTML 2024-03-01 23:25:29 +00:00

README.md

Salix Logo

 

Go Reference Go Report Card

Salix (pronounced say-lix) is a Go templating engine inspired by Leaf.

Salix's syntax is similar to Leaf and (in my opinion at least), it's much more fun to write than the Go template syntax. If you like this project, please star the repo. I hope you enjoy! :)

Table of contents

Examples

Template

<html>
    <head>
        <title>#(page.Title)</title>
    </head>
    <body>
        #for(i, user in users):
        <div>
            <h2>#(toLower(user.Name))</h2>
            <p>User ID: #(i)</p>
            #if(user.LoggedIn): <p>This user is logged in</p> #!if
            #if(user.IsAdmin): <p>This user is an admin!</p> #!if
            <p>Registered: #(user.RegisteredTime.Format("01-02-2006"))</p>
        </div>
        #!for
    </body>
</html>

API Usage

t, err := salix.New().ParseFile("example.salix.txt")
if err != nil {
  panic(err)
}

err = t.WithVarMap(vars).
    WithTagMap(tags).
    WithEscapeHTML(true).
    Execute(os.Stdout)
if err != nil {
  panic(err)
}

See the examples directory for more examples.

Tags

In Salix, tags have full control over the Abstract Syntax Tree (AST), which allows them to do things the language wouldn't ordinarily allow. Salix's if statements, for loops, macros, includes, etc. are implemented as tags.

Creating custom tags

You can extend the capabilities of Salix by creating custom tags. To create a custom tag, you need to implement the salix.Tag interface and add it to the tag map of your template or namespace using the WithTagMap method.

Salix tags follow a distinctive syntax pattern. They start with a pound sign (#), followed by a name and optional arguments. Tags can also enclose a block of content, and if they do, the block is terminated by an end tag with the same name. Here's an example of a template with both a macro tag and an include tag:

#macro("example"):
    Content
#!macro

#include("template.html")

In this example:

  • The macro tag has a block, indicated by the content enclosed between #macro("example"): and #!macro.
  • The include tag doesn't have a block; it simply includes the content of template.html.

for tag

Salix's for tag is used for iterating over slices, arrays, and maps. It can assign one or two variables depending on your needs. When using a single variable, it sets that variable to the current element in the case of slices or arrays, or the current value for maps. With two variables, it assigns the first to the index (in the case of slices or arrays) or the key (for maps), and the second to the element or value, respectively. Here's an example of the for tag in action:

#for(id, name in users):
	Name: #(name)
	ID:   #(id)
#!for

if tag

The if tag in Salix allows you to create conditional statements within your templates. It evaluates specified conditions and includes the enclosed content only if the condition is true. Here's an example:

#if(weather.Temp > 30):
	<p>It's a hot day!</p>
#elif(weather.Temp < 0):
	<p>It's freezing!</p>
#else:
	<p>The temperature is between 0 and 30</p<
#!if

include tag

The include tag allows you to import content from other templates in the namespace, into your current template, making it easier to manage complex templates. Here's an example of the include tag:

#include("header.html")

Using the include tag with extra arguments

The include tag can accept extra local variables as arguments. Here's an example with a title variable:

#include("header.html", title = "Home")

These local variables will then be defined in the included template.

macro tag

The macro tag is a powerful feature that allows you to define reusable template sections. These sections can be included later in the current template or in other templates that were included by the include tag. Here's an example of the macro tag:

#macro("content"): <!-- This defines a macro called "content" -->
    Content
#!macro

#macro("content") <!-- This inserts the content macro -->

When a macro tag has a block, it sets the macro's content. When it doesn't, it inserts the contents of the macro. In the above example, a macro is defined and then inserted.

Using the macro tag with extra arguments

Similar to the include tag, the macro tag can accept extra local variables as arguments. You can define these variables when including the macro. Here's an example:

#macro("content", x = 1, y = x + 2)

Functions

Functions used in a template can accept any number of arguments but are limited to returning a maximum of two values. When a function returns two values, the second one must be an error value.

Global Functions

Salix includes several useful global functions in all templates:

  • len(v any) int: Returns the length of the value passed in. If the length can't be found for the value passed in, it returns an error.
  • json(v any) string: Returns a JSON string for the value passed in.
  • toUpper(s string) string: Returns s, but with all characters mapped to their uppercase equivalents.
  • toLower(s string) string: Returns s, but with all characters mapped to their lowercase equivalents.
  • hasPrefix(s, prefix string) bool: Returns true if s starts with prefix.
  • trimPrefix(s, prefix string) string: Returns s, but with prefix removed from the beginning.
  • hasSuffix(s, suffix string) bool: Returns true if s ends with suffix.
  • trimSuffix(s, suffix string) string: Returns s, but with suffix removed from the end.
  • trimSpace(s string) string: Returns s, but with any whitespace characters removed from the beginning and end.
  • equalFold(s1, s2 string) bool: Returns true if s1 is equal to s2 under Unicode case-folding, which is a general form of case-insensitivity.
  • count(s, substr string) int: Returns the amount of times that substr appears in s.
  • split(s, sep string) []string: Returns a slice containing all substrings separated by sep.
  • join(ss []string, sep string) string: Returns a string with all substrings in ss joined by sep.
  • replace(s, old, new string, n int): Returns a string with n occurrences of old in s replaced with new.
  • replaceAll(s, old, new string): Returns a string with all occurrences of old in s replaced with new.

Adding Custom Functions

You can include custom functions as variables using the WithVarMap method on templates or namespaces. Methods that fit the above conditions can also be used as template functions.

Expressions

Salix's expressions mostly work like Go's, but there are some extra features worth mentioning.

Ignoring errors

If you'd like to ignore errors in an expression tag, you can do that by adding a question mark after the pound symbol.

<!-- This would return an error if example wasn't defined or if it didn't have an Example() method -->
#(example.Example())

<!-- This would ignore any error and keep executing the rest of the template -->
#?(example.Example())

Ternary Expressions

Salix supports ternary expressions, which allow you to choose a value based on whether a condition is true. For example:

#(len(matches) > 1 ? "several matches" : "one match")

This example returns "several matches" if the length of matches is greater than one. Otherwise, it returns "one match".

Coalescing operator

The coalescing operator allows you to return a default value if a variable isn't defined. Here's an example:

<title>#(title | "Home")</title>

In this case, the expression will return the content of the title variable if it's defined. If not, it will return "Home" as the default value.

The in operator

Salix's in operator allows you to check if a slice or array contains an element, if a map contains a key, or if a string contains a substring. Here's one example:

#("H" in "Hello") <!-- Returns true -->

Acknowledgements

  • Pigeon: Salix uses a PEG parser generated by pigeon. Salix would've been a lot more difficult to write without it.
  • Leaf: Leaf was the first templaing language I ever used, and it inspired a lot of the syntax I've implemented in Salix because I found it really fun to use.