gamebox / gwirl Goto Github PK

Integrate with gopls and provide semantic highlighting and autocomplete, linting, compiler errors, etc.

Do we want to support multiple content transclusions? Some things like a base layout may want to allow a consumer to transclude HTML for things like head content, body content, and footer content.

Currently only if is supported, but adding if else and else support should be relatively simple. This should be done as soon as possible.

Need some kind of distinctive branding for the language before we create the website.

• Brand colors
• Logo
• Font(s)

Kind of a gap from Twirl, implement safe go expression syntax:

THis is a string that I want to appear verbatim, @(someValue.someMethod().value).

Notice that the parens demarcate the boundary of the expression, which is useful for usages where the expression is followed by a valid character in a Go expression.

Create a lightweight Static Site generation tool on top of Gwirl and use it to publish a GitHub pages site for Gwirl.

Or create a function that takes an empty interface and then use reflect to do the "right thing" with it.

At first support

• Neovim
• VSCode

Eventually we will support

• GoLand

We would like to have it so that @} (and new to the language @{) are needed solely for escaping unbalanced squirly braces. Balanced braces can be written as Whatever Supreme Power You Believe In intended.

This is the highest priority thing to do, as it is likely considered a bug that this does not happen today. We can probably start with using something like

sb.WriteString(html.HTMLEscapeString(fmt.Sprintf("%v", /* expression */)))

And then refine from there, we'd probably want to extract that to a GwirlEscaped function in the package along with GwirlRaw

Right now all templates need to be written at the top level of the templates directory, as we don't traverse any subdirectories.

Should Gwirl support writing your Gwirl files in any directory, and have the _gwirl.go files be output in that same package?

Pros

• Not so strict, and allows for better organization to meet a specific projects need
• Removes the chance of conflict with existing project structure.

Cons

• Requires us to search through an entire project for .gwirl files