Skip to content
Liquid markup language. Safe, customer facing template language for flexible web apps.
Ruby Liquid
Branch: master
Clone or download

Latest commit

tjoyal Merge pull request #1257 from Shopify/StaticRegisters/remove-register…

[StaticRegisters] Remove registers attr_reader
Latest commit 1865452 May 22, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Enable CLA bot Oct 19, 2018
example/server Add ForceEqualSignAlignment to .rubocop.yml (#1190) Oct 21, 2019
lib [StaticRegisters] Remove registers attr_reader May 22, 2020
performance Upgrade rubocop and style guide for ruby 2.7 compatibility Jan 9, 2020
test [StaticRegisters] Remove assertion for delete to not remove static co… May 22, 2020
.gitignore render_to_output_buffer Apr 23, 2019
.rubocop-https---shopify-github-io-ruby-style-guide-rubocop-yml Upgrade rubocop and style guide for ruby 2.7 compatibility Jan 9, 2020
.rubocop.yml Use `Regexp#match?` when `MatchData` is not used (#1165) Sep 19, 2019
.rubocop_todo.yml style: Avoid deep nesting for parsing the liquid tag in the block body Jan 10, 2020
.travis.yml [Travis] Optional head May 21, 2020 Grammatic and other fixes to Feb 3, 2016
Gemfile Upgrade rubocop and style guide for ruby 2.7 compatibility Jan 9, 2020 [StaticRegisters] Fetch raise on missing May 22, 2020
LICENSE Rename MIT-LICENSE to LICENSE Oct 14, 2015 Update readme Sep 10, 2019
Rakefile Add ForceEqualSignAlignment to .rubocop.yml (#1190) Oct 21, 2019
liquid.gemspec Enabled frozen string literals (#1154) Sep 18, 2019

Build Status Inline docs

Liquid template engine


Liquid is a template engine which was written with very specific requirements:

  • It has to have beautiful and simple markup. Template engines which don't produce good looking markup are no fun to use.
  • It needs to be non evaling and secure. Liquid templates are made so that users can edit them. You don't want to run code on your server which your users wrote.
  • It has to be stateless. Compile and render steps have to be separate so that the expensive parsing and compiling can be done once and later on you can just render it passing in a hash with local variables and objects.

Why you should use Liquid

  • You want to allow your users to edit the appearance of your application but don't want them to run insecure code on your server.
  • You want to render templates directly from the database.
  • You like smarty (PHP) style template engines.
  • You need a template engine which does HTML just as well as emails.
  • You don't like the markup of your current templating engine.

What does it look like?

<ul id="products">
  {% for product in products %}
      <h2>{{ }}</h2>
      Only {{ product.price | price }}

      {{ product.description | prettyprint | paragraph }}
  {% endfor %}

How to use Liquid

Install Liquid by adding gem 'liquid' to your gemfile.

Liquid supports a very simple API based around the Liquid::Template class. For standard use you can just pass it the content of a file and call render with a parameters hash.

@template = Liquid::Template.parse("hi {{name}}") # Parses and compiles the template
@template.render('name' => 'tobi')                # => "hi tobi"

Error Modes

Setting the error mode of Liquid lets you specify how strictly you want your templates to be interpreted. Normally the parser is very lax and will accept almost anything without error. Unfortunately this can make it very hard to debug and can lead to unexpected behaviour.

Liquid also comes with a stricter parser that can be used when editing templates to give better error messages when templates are invalid. You can enable this new parser like this:

Liquid::Template.error_mode = :strict # Raises a SyntaxError when invalid syntax is used
Liquid::Template.error_mode = :warn # Adds errors to template.errors but continues as normal
Liquid::Template.error_mode = :lax # The default mode, accepts almost anything.

If you want to set the error mode only on specific templates you can pass :error_mode as an option to parse:

Liquid::Template.parse(source, :error_mode => :strict)

This is useful for doing things like enabling strict mode only in the theme editor.

It is recommended that you enable :strict or :warn mode on new apps to stop invalid templates from being created. It is also recommended that you use it in the template editors of existing apps to give editors better error messages.

Undefined variables and filters

By default, the renderer doesn't raise or in any other way notify you if some variables or filters are missing, i.e. not passed to the render method. You can improve this situation by passing strict_variables: true and/or strict_filters: true options to the render method. When one of these options is set to true, all errors about undefined variables and undefined filters will be stored in errors array of a Liquid::Template instance. Here are some examples:

template = Liquid::Template.parse("{{x}} {{y}} {{z.a}} {{z.b}}")
template.render({ 'x' => 1, 'z' => { 'a' => 2 } }, { strict_variables: true })
#=> '1  2 ' # when a variable is undefined, it's rendered as nil
#=> [#<Liquid::UndefinedVariable: Liquid error: undefined variable y>, #<Liquid::UndefinedVariable: Liquid error: undefined variable b>]
template = Liquid::Template.parse("{{x | filter1 | upcase}}")
template.render({ 'x' => 'foo' }, { strict_filters: true })
#=> '' # when at least one filter in the filter chain is undefined, a whole expression is rendered as nil
#=> [#<Liquid::UndefinedFilter: Liquid error: undefined filter filter1>]

If you want to raise on a first exception instead of pushing all of them in errors, you can use render! method:

template = Liquid::Template.parse("{{x}} {{y}}")
template.render!({ 'x' => 1}, { strict_variables: true })
#=> Liquid::UndefinedVariable: Liquid error: undefined variable y

Usage tracking

To help track usages of a feature or code path in production, we have released opt-in usage tracking. To enable this, we provide an empty Liquid:: Usage.increment method which you can customize to your needs. The feature is well suited to However, the choice of implementation is up to you.

Once you have enabled usage tracking, we recommend reporting any events through Github Issues that your system may be logging. It is highly likely this event has been added to consider deprecating or improving code specific to this event, so please raise any concerns.

You can’t perform that action at this time.