Since Python 3.7 dicts must preserve insertion order in all implementations (in Python 3.6 it was only an implementation detail in CPython). Thus I think it would make sense to state this in the loop section of the docs which currently states the following:

Note, however, that Python dicts are not ordered; so you might want to ei

@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.

Environment

• blade: 2.0.5-RELEASE
• jdk: 1.8.0_111
• maven: 3.3.9
• OS: Windows 7 Home Basic

Description

When I tried to upload a file, an java.lang.UnsupportedOperationException: direct buffer raised, so that the upload operation cannot be done. The full exception stack is as follows:

java.lang.UnsupportedOperationException: direct buffer
	at io.netty.buffer.Po

Pretty much the first link in the guide, to download the latest version of rivets.js, is a broken link. It's this one:

You can grab the latest stable release here or install

When you throw an exception (throw new \Exception('Some error...');) in CLI mode the script silently dies without no output to the console. It is only logged in PHP's error log.

That should not be default behaviour I would say.

Btw, this is on Windows. If I run it in my Linux environment it should just fine.

Hello,

as in Issue #689 described, the tags used in Text-Mode adds a line-break. Maybe it's intended behavoir. But then the documentation should be corrected
From the Documentation https://www.thymeleaf.org/doc/tutorials/3.0/usingthymeleaf.html#textual-syntax:

Dear [(${customer.name})],

This is the list of our products:

[# th:each="prod : ${products}"]
   - 

this package is such a great find. thanks so much for your work. Just a few suggestions

1. notwithstanding the assumption that folks are experienced go developers, it might be a good idea to mention that function names in the template must be capitalized to be accessible.

2. the use of ./template doesn't work if you are using go build .. I have a directory that I keep both the source an

• Improve documentation on how to author templates.
• Add documentation on the packaging and distributing of WinTS compatible templates. This must also include differences from how dotnet-new works with template sources.
• Improve tools to help with testing and validating any created templates. Existing tests and tools are a start but these may need updating and revising to make them

The link to Django version compatibility 1.7 in the README's Development status section is broken, it looks like this version is not supported anymore: https://docs.djangoproject.com/en/1.7/ref/templates/builtins/

I suggest to either include a reference of actually implemented filters in your project's documentation, or ensure support for Django 1.8 or higher so you can link to their document

Your documentation says that it defaults to "template" for the package name. It should default to the name of the destination directory.

When rendering with an invalid template that refers to an Object instead of strings/integers/bools/arrays, the rendering silent fails by rendering "[object]", due to:
https://github.com/Keats/tera/blob/b91a985951fccf6896c7192ea7c78ba64608bb62/src/context.rs#L119
(by the way, this could be Cow::Borrowed)

This is does not match the rust philosophy of being explicit and quickly failing so

Describe the bug
Extension method not working as expected.

To Reproduce

[Fact]
public async Task Should_Compile_Template()
{
	var engine = new RazorLightEngineBuilder()
		.UseMemoryCachingProvider()
		.Build();

	var template = "@using Humanizer@(Model.Name.Pluralize())";
	var component = new Component { Name = "Customer"};
	var result = await engine.CompileRende

See #128.

This was implemented a while ago, but there's no documentation for it.

Reproduction:

=> (sp/render "{{ props.docs|default:@props.notes }}"
              {:props {}})
"@props.notes"

In the templates I’m writing, I had expected the filter to return either nil or a blank string.

@yogthos I’m not sure if we should consider this a bug or a feature request, but either way, what do you think?

Hi, I was trying to build a simple use case and at first glance Scalate seemed to be the great engine for the job. But when I tried to understand how to use it in my scala code I found it not so easy to use essentially because of the missing documentation.
I had to rely on test use cases which help but not as much as a proper documentation should.

My simple scenario was taking an input file in