Skip to content

Commit

Permalink
Small edit to readme to show dependency tree
Browse files Browse the repository at this point in the history
  • Loading branch information
mitsuhiko committed Aug 30, 2022
1 parent 2e37b6e commit 6cd21be
Showing 1 changed file with 14 additions and 7 deletions.
21 changes: 14 additions & 7 deletions README.md
Expand Up @@ -5,7 +5,7 @@
[![Build Status](https://github.com/mitsuhiko/minijinja/workflows/Tests/badge.svg?branch=main)](https://github.com/mitsuhiko/minijinja/actions?query=workflow%3ATests)
[![License](https://img.shields.io/github/license/mitsuhiko/minijinja)](https://github.com/mitsuhiko/minijinja/blob/main/LICENSE)
[![Crates.io](https://img.shields.io/crates/d/minijinja.svg)](https://crates.io/crates/minijinja)
[![rustc 1.43.0](https://img.shields.io/badge/rust-1.45%2B-orange.svg)](https://img.shields.io/badge/rust-1.45%2B-orange.svg)
[![rustc 1.45.0](https://img.shields.io/badge/rust-1.45%2B-orange.svg)](https://img.shields.io/badge/rust-1.45%2B-orange.svg)
[![Documentation](https://docs.rs/minijinja/badge.svg)](https://docs.rs/minijinja)

</div>
Expand All @@ -14,12 +14,19 @@ MiniJinja is a powerful but minimal dependency template engine for Rust which
is based on the syntax and behavior of the
[Jinja2](https://jinja.palletsprojects.com/) template engine for Python.

It's implemented on top of `serde` and only has it as a single dependency. It
supports a range of features from Jinja2 including inheritance, filters and
more. The goal is that it should be possible to use some templates in Rust
programs without the fear of pulling in complex dependencies for a small
problem. Additionally it tries not to re-invent something but stay in line
with prior art to leverage an already existing ecosystem of editor integrations.
It's implemented on top of `serde` and only has it as a single required
dependency. It supports a range of features from Jinja2 including inheritance,
filters and more. The goal is that it should be possible to use some templates
in Rust programs without the fear of pulling in complex dependencies for a small
problem. Additionally it tries not to re-invent something but stay in line with
prior art to leverage an already existing ecosystem of editor integrations.

```
$ cargo tree
minimal v0.1.0 (examples/minimal)
└── minijinja v0.18.1 (minijinja)
└── serde v1.0.144
```

## Example Template

Expand Down

0 comments on commit 6cd21be

Please sign in to comment.