@fabpot Is there a way to build the Twig documentation locally to test changes before submitting them? I cannot find the sphinx config file in the repo.

I've got a project that uses JSDOM for some server-side DOM processing, and tests that emulated that environment by me adding JSDOM globals to Node's global scope and then using hyperscript to whip up some mock DOM trees. However, I recently came across some advice from the JSDOM authors (also repeated on sever

It would be helpful to have a copy of the "How to get started" readme section as a fully laid out examples directory where someone could just drop in and do cargo run and see everything work.

It would be really useful if gomplate could have native support for accessing terraform output values. Using the terraform CLI this can easily be done using terraform output -json some_output_value. Having the ability to access terraform state using a data source would be pretty useful when performing various templating tasks!

I've had a few issues with this, the latest one being this part from the ScriptObject documentation:

"Notice that when using a function with pipe calls like {{description | string.strip }}``, the last argument passed to the string.strip` function is the result of the previous pipe. That's a reason why you will notice in all builtin functions in scriban that they usually take the most relevant p

I'm using Rocker to render files of various extensions and after some reading of the source, I found out the files have to end in .raw or .html. I couldn't find anywhere that documented that requirement so I'm creating this issue to track that.

Also I would like to propose allowing for any file that ends in .rocker to be processed with a raw content type.

Can't have "template" folder in function folder

Expected Behaviour

This function stopped working at this commit, renaming template to templates fixed the issue

https://gi

Escaping is not contextual and HTML escaping is used in every context. This might lead newcomers to think that it is safe to interpolate user controlled data in a page, leading to XSS.

I think it would be better to point out in README or documentation that this package does not aim to protect users from XSS but just implements a rudimentary escaping mechanism.

Since some gophers might be use

It's unclear from the result that when a user includes a non-YAML template and the destination is standard out, that its output is not included on purpose.

Let's give them a hint. For example, on stderr, we could say,

There are templates marked for output that are not included in this output.
Non-YAML templates are not rendered to standard output.
If you want to include those results, u

Description

We have a job that requires a monotonically increasing port assignment for each allocation.
Our current idea is to use NOMAD_ALLOC_INDEX as follows:

job "foo" {
  datacenters = ["bar"]

  group "foo" {
    count = 3

    task "foo-${NOMAD_ALLOC_INDEX}" {
      driver       = "docker"

      config {
        image        = "foo"
        network_mode = "ho

Split from #46.

• remove -t/--template and the hierarchy layer between templates and config.yaml
• add switch to chose which config file to use, default config.yaml
• add interactive auto-upgrade routine if no config.yaml but a i3 template dir is found

I can't run readme anymore after updating node from v8 to v10...

node: v10.14.1
npm: v6.4.1
OS: MacOS Sierra

A@anthony:~/git/someproject (master) $ readme
Markserv boot: starting Markserv...
path.js:39
throw new ERR_INVALID_ARG_TYPE('path', 'string', path);
^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object
a

if i coalesce .settings.variable .config.variable and only the .config directive exists in the file, it fails before even checking .config because .settings is not in the file.

This really defeats the entire purpose of checking the first non-null value.

Is your feature request related to a problem?

1. Managing all k8s resources in a single file becomes difficult to maintain for larger projects
2. Executing drone-gke multiple times for each individual file seems a bit excessive

Describe the solution you'd like

An API to drone-gke that is compatible with kubectl apply's -f / --filename argument:

-f, --filename=[]: Fi

Would be nice to know, since all flux:field.* viewhelpers are deprecated and are removed in v10.

So for example, how to migrate flux:field.inline.fal to flux:field?

Is your feature request related to a problem? Please describe.
Proji currently only supports TOML as config file format. Since it's quite possible that proji will work with APIs in the future (#63), you should be able to export/import configs in JSON format as well.

Describe the solution you'd like
Add a flag to class config related commands. TOML might stay the default format f