Hi,

I see no activities (interest) for this project in the last period of time? They are many PR and issues with no resolution or comment. @mbosecke Do you intent to continue working on this project? Any information from maintainers about the next steps/releases is very welcome.

Hi everyone,

I just released a SNAPSHOT of next major version (3.0.0-SNAPSHOT) for both pebble and pebble-spring in the snapshot repository of sonatype. If anyone is interested in trying it, you can just add the following code in your pom.xml to retrieve SNAPSHOT versions

  <repositories>
    <repository>
      <id>sonatype-public</id>
      <name>Sonatype Public</name>
      <url>https://oss.sonatype.org/content/groups/public</url>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </repository>
  </repositories>

After that, just change your pebble dependency to 3.0.0-SNAPSHOT

      <dependency>
        <groupId>io.pebbletemplates</groupId>
        <artifactId>pebble</artifactId>
        <version>3.0.0-SNAPSHOT</version>
      </dependency>

Waiting for your comments on it !

Orchid is a tool I recently released which is perfect for managing the documentation of Java projects, and Pebble is the ideal candidate. Orchid itself uses Pebble as its primary template engine, so setting up Pebble with Orchid docs not only will improve the documentation as a whole, but also serve as a great example of what can be done with Pebble.

This issue will track my progress getting Pebble set up with Orchid, and also serve as a discussion around the site.

Progress

• [x] Landing page(s)
• [x] Full wiki, migrated from the current Github Wiki
• [x] Auto-generated listings of/documentation for:
  • [x] Tags
  • [x] Filters
  • [x] Functions
  • [x] Tests
  • [x] Operators
• [x] Complete Javadoc API documentation
• [x] Changelog
  • [ ] Link to older versions of docs
• [x] Automatic build/deploy from Travis CI to Github Pages
  • [x] Host each version's docs in a subfolder to maintain docs history

Discussion Points

• Orchid runs as a Gradle plugin, so using Orchid will require Pebble to either migrate from Maven to Gradle as its sole build system, or use both in the same project (Maven for normal build/test, Gradle for Orchid build). Alternatively, I would like to build a Maven plugin eventually but don't know how; if anyone has experience/would like to help out building a Maven Orchid plugin, we could continue using only Maven here
• What should the site look like? Keep the theme used for the current docs, use a default Orchid theme, or find/create a new theme just for Pebble

https://github.com/JavaEden/Orchid

This PR adds a new maven project in docs/ which will generate a documentation site and deploy it to Github Pages, using Orchid. The site includes a wiki (migrated from the current Github Wiki) and Javadocs documentation, and also includes a basic full-text search of site content. You can preview the site here. It's pretty basic overall, using one of the built-in themes, but I'm more than happy to make any changes as needed.

Here's a brief rundown of the new functionality (will still need to be integrated into the current release process):

Commands (run from docs/ directory)

• mvn orchid:serve - build the site and serve it locally on http://localhost:8080. Changes to site content will rebuild the site.
• mvn -Denvironment=prod orchid:deploy - build the site and deploy it to Github Pages. Requires an API token with push access to the repo, set as githubToken in the environment variables. The environment project property will optimize the build for production.

Directory Structure

• docs/src/orchid/resources - The main root for site content.
  • site/src/orchid/resources/pages - Arbitrary static pages
  • site/src/orchid/resources/wiki - A summary.md file in here declares the pages in the wiki, which are other files relative to this directory. They will automatically be linked to each other in the order they are defined in the summary file.
  • site/src/orchid/resources/homepage.md - The content for the front page of the site.
  • site/src/orchid/resources/config.yml - Configuration for things like site menus, and theme/plugin options.

Deployment

Orchid builds the site into the docs/target/docs/orchid directory. It has a publication mechanism in it to deploy to Github Pages after a successful build, which creates a temporary directory to do all the git stuff and shouldn't break anything when deploying. It's set up to clean out and force push to the branch, but it has options to maintain history, and also to push each version to a new subdirectory to maintain historical site versions if that is desired.

I've never worked with Maven so I don't know if this is the correct way to set up the docs project, but everything's working great using the Orchid Maven plugin while in the docs/ directory. Huge thanks to @bjansen for creating the Maven plugin for this!

In a typical web scenario you want to add external resources (e.g. CSS, JavaScript etc.) to the produced output.

For HTML5 all CSS resources should be placed within the 'head' tag. The JavaScript resources should be placed before the closing 'body' tag to improve the speed of the loading. Additionally those resources should be combined together into one file to reduce the number of HTTP requests to the server, because the browser is allowed only to open two connections per domain (see HTTP specification).

Hence whats happening is typically all resources are manually combined and added to the template. But this is hard with twig since you will add more resources in other child templates. E.g. there is a base.twig from which all other templates extends. From a practical standpoint of view it would be easier when each sub template and included template can add new resources and the base.twig does not need to know anything about the additional resources. This way only those resources are included in the HTML page which are actually required and not all potential resources which eventually are required.

We are currently implementing such a solution. Is there any interest that I create a pull request for this feature?

Hello,

When dealing with macros, sometimes we need to hold a value in variable to use it more than once.

For example;

{% macro toggleMacro(itemInfo) %}
{% set productId = itemInfo.item.productId %}
<input type="radio"
       class="select-radio hide"
       checked="true"
       value="{{ currentUnit }}"
       name="{{ 'unit_' + productId }}"/>
{% endmacro %}

but setting a new productId variable, will also override current productId variable if exists in context. I know it can be useful to reach all context, but I think we need to also support local variables.

May be {% set local foo = bar %} for example?

Hi,

Guava is a tricky dependency. Large projects can have multiple dependencies to libraries that depend on different Guava versions and cause conflicts.

I see there's a plan to switch to Caffeine (great!) for Pebble 3.0, but I guess this means in a pretty far future.

Instead, would you be interested in a contribution to introduce a cache abstraction, with Guava and Caffeine based implementations (Caffeine only being an optional dependency)? This way, Guava would still be the default, at least in Pebble 2, but users could prefer passing Caffeine based caches instead and exclude the Guava dependency.

Please let me know.

When an expression is at the end of a line, there seems to be no newline character to seperate that line with the next line.

<html>
  <body>
    <div id="content">
      {{ mainContent }}
    </div>
  </body>
</html>

In the previous example, given that the mainContent variable will be replaced with "Hello, world", the output will be:

<html>
  <body>
    <div id="content">
      Hello, world    </div>
  </body>
</html>

As you can see, there is no newline after "Hello, world". The </div> closing tag with its four spaces of indentation should be on the next line, not on the same line that "Hello, world" is on.

I have a CompanyService with a method get(long id):Company, I injected the companyService in my template model and I I try something like this:

{% for customer in customers %}
<tr>
   <td>{{ companyService.get(customer.companyId) }}</td>
</tr>
{% endfor %}

where Customer has a property Long companyId (my idea is to create a quick prototype of application without a fat CustomerDto that contains a Company). The result is an empty ("") string without any message in console. Any idea?

using pebble to generate non web files, would be useful to have an extension that could be used to also recognize as pebble, for example in intellij's plugin. This is more of a doc, spec, spread the word thing.

I'm a new to pebble and I want to used it with spring boot so I follow this wiki guide: https://github.com/PebbleTemplates/pebble/wiki/spring-boot-integration

I use this dependecy:

<dependency>
    <groupId>io.pebbletemplates</groupId>
    <artifactId>pebble-spring-boot-starter</artifactId>
    <version>2.5.1</version>
</dependency>

Then place pebble templates(index.pebble) in /src/main/resources/templates Then make a controller:

@Controller
public class DemoController {
    
    @RequestMapping("/pebble")
    public String index(Model model){
        model.addAttribute("name", "John Doe");
        return "index";
    }
}

After running the app here's the error I got:

org.springframework.beans.factory.BeanDefinitionStoreException: Failed to process import candidates for configuration class [com.pebbletry.demo.DemoApplication]; nested exception is java.lang.IllegalStateException: Could not evaluate condition on org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration due to org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure your own configuration does not rely on that class. This can also happen if you are @ComponentScanning a springframework package (e.g. if you put a @ComponentScan in the default package by mistake)
	at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:648) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.lambda$processDeferredImportSelectors$2(ConfigurationClassParser.java:567) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at java.util.ArrayList.forEach(ArrayList.java:1257) ~[na:1.8.0_172]
	at org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:563) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:188) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:316) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:233) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:273) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:93) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:694) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:532) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) ~[spring-boot-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759) [spring-boot-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:395) [spring-boot-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:327) [spring-boot-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255) [spring-boot-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243) [spring-boot-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at com.pebbletry.demo.DemoApplication.main(DemoApplication.java:10) [classes/:na]
Caused by: java.lang.IllegalStateException: Could not evaluate condition on org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration due to org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure your own configuration does not rely on that class. This can also happen if you are @ComponentScanning a springframework package (e.g. if you put a @ComponentScan in the default package by mistake)
	at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:55) ~[spring-boot-autoconfigure-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:108) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:221) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.processMemberClasses(ConfigurationClassParser.java:362) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:265) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:245) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:638) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE]
	... 17 common frames omitted
Caused by: java.lang.NoClassDefFoundError: org/springframework/boot/bind/RelaxedPropertyResolver
	at com.mitchellbosecke.pebble.boot.autoconfigure.PebbleTemplateAvailabilityProvider.isTemplateAvailable(PebbleTemplateAvailabilityProvider.java:16) ~[pebble-spring-boot-starter-2.5.1.jar:na]
	at org.springframework.boot.autoconfigure.template.TemplateAvailabilityProviders.findProvider(TemplateAvailabilityProviders.java:158) ~[spring-boot-autoconfigure-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.autoconfigure.template.TemplateAvailabilityProviders.getProvider(TemplateAvailabilityProviders.java:145) ~[spring-boot-autoconfigure-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration$ErrorTemplateMissingCondition.getMatchOutcome(ErrorMvcAutoConfiguration.java:194) ~[spring-boot-autoconfigure-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47) ~[spring-boot-autoconfigure-2.0.2.RELEASE.jar:2.0.2.RELEASE]
	... 23 common frames omitted
Caused by: java.lang.ClassNotFoundException: org.springframework.boot.bind.RelaxedPropertyResolver
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[na:1.8.0_172]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_172]
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) ~[na:1.8.0_172]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_172]
	... 28 common frames omitted

Given the following macro saved in the file forms.html:

{% macro input(type="text") %}
    <input type="{{ type }}"  />
{% endmacro %}

If you import forms.html without assigning the import to a variable then using named arguments works fine, e.g:

{% import "forms" %}
{{ input(type="text") }}

But if you import forms.html and set it as a variable then passing named arguments throws a ParserException with the message "Can not use named arguments when calling a bean method", e.g.

{% import "forms" as forms %}
{{ forms.input(type="text") }}

Hello,

since this morning security checks in our projects are reporting new critical vulnerability in the current pebble version 3.1.5: NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-37767 Original report: https://github.com/Y4tacker/Web-Security/issues/3

Any short-term workaround to mitigate the vulnerability?

inside embed block

{% embed %}
{% endembed %}

even if the string inside the bracket is XXS code written in javascript, it doesn't escape and execute the script

For example, I am adding userName to the model and I know I can access the value by {{ userName }} in my template. But I want to list all defined variables (keys) in a template like {{ _context.key }} {{ _context.value }} and see in my template something like userName: Jhon Doe.

Is that possible? Or is there a way to see all defined variables in a template?

I am using pebble templates and it works perfectly. Easy setup and quick to go. I am running into 1 small issue. I want to pass html to 1 of my templates using parameters like this:

pebbleTemplate.evaluate(writer, parameters);

I am using pebble to create html emails and I want to allow breaklines (
) in my email. How can I pass html to a template and not have the < and > symbols escaped?

Thanks in advance Martijn