Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix missing yaml front matter colon and adjust/add clarifying language. #8250

Merged
merged 1 commit into from Jun 13, 2020
Merged

Fix missing yaml front matter colon and adjust/add clarifying language. #8250

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/_docs/configuration/liquid.md
View file
Open in desktop
Expand Up @@ -6,16 +6,18 @@ Liquid's response to errors can be configured by setting `error_mode`. The
options are

- `lax` --- Ignore all errors.
- `warn` --- Output a warning on the console for each error.
- `warn` --- Output a warning on the console for each error. (default)
- `strict` --- Output an error message and stop the build.

Within _config.yml, this could be configured as follows:
Within _config.yml, the default configuration is as follows:

```yaml
liquid:
error_mode: warn
```

The above example depicts the "warn" value, which is already set by default- `error_mode: warn`. This results in any issues being called out during the build process however will continue to build if possible.

You can also configure Liquid's renderer to catch non-assigned variables and
non-existing filters by setting `strict_variables` and / or `strict_filters`
to `true` respectively. {% include docs_version_badge.html version="3.8.0" %}
Expand All @@ -28,9 +30,9 @@ An example of setting these variables within _config.yml is as follows:

```yaml
liquid:
error_mode strict
error_mode: strict
strict_variables: true
strict_filters: true
```

Configuring as described above will stop a build/serve from happening and instead call out the offending error and halt. This is helpful when desiring to catch liquid-related issues by stopping the build or serve process and forcing you to deal with it.
Configuring as described above will stop your build/serve from happening and call out the offending error and halt. This is helpful when desiring to catch liquid-related issues by stopping the build or serve process and allowing you to deal with any issues.