Nunjucks docs !== jinja docs
See original GitHub issueI was looking through the docs for the replace
filter, since it now supports regex, but couldn’t find anything in Jinja about it. After diving into the github issues I finally figured out the syntax (r/body/flags
rather than javascript’s /body/flags
), and I wanted to add that to the documentation, but it looks like nunjucks just links to Jinja’s docs.
It seems like, at least for the filters, Nunjucks is diverting from Jinja. Probably more than just the little issue I saw. Should separate api docs be maintained, or should there be a push to update Jinja to conform to Nunjucks’ spec?
Issue Analytics
- State:
- Created 9 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
nunjucks templating docs
This is an overview of the templating features available in Nunjucks. Nunjucks is essentially a port of jinja2, so you can read their...
Read more >Template Language—Nunjucks — Eleventy
Read more on the Nunjucks documentation or relevant discussion on Eleventy Issue #1060. Other pages in Template Languages: HTML · Markdown · WebC...
Read more >nunjucks - npm
Nunjucks is a full featured templating engine for javascript. It is heavily inspired by jinja2. View the docs here.
Read more >Nunjucks/Jinja - alternative for `include` when access to scope ...
According to Nunjucks documentation,. an include is not a pre-processor that pulls the included template code into the including template ...
Read more >nunjucks | Yarn - Package Manager
Nunjucks is a full featured templating engine for javascript. It is heavily inspired by jinja2. View the docs here. Installation. npm install nunjucks....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Probably opening a new ticket with a clear description of the problem and the preferred resolution (or even better, a PR to fix the issue) would be more useful than reopening this one.
@rhengles Can you clarify specifically what it is that you think needs to be done about the regular expressions docs?