Update dependency teddy to v1.2.1 - #301
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/teddy-1.x
branch
from
August 27, 2026 21:28
eee0771 to
572195c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.1.4→1.2.1Release Notes
rooseveltframework/teddy (teddy)
v1.2.1Compare Source
<include>tags inside a<loop>so that the included partial's<if>,<unless>, one line conditionals, and nested<loop>tags can read the loop'skeyandval. Previously the partial's contents were parsed against the model as it stood outside the loop, so a partial could print the loop'svalthrough a{variable}but any tag that branched on it behaved as though it were not there. Includes are now expanded by the loop, once per iteration, against that iteration's model, which is how partials behave in other templating engines.v1.2.0Compare Source
teddy.clearTemplates()was called. Caching is now off by default, which is how most other templating engines (e.g. ejs or pug) treat their own caching, so a template that changes on disk is picked up on the next render.view cachesetting, which it enables in production and disables in development, and Teddy now uses it. That means production keeps caching and development stops needing a restart.teddy.setTemplateare unaffected. Those are always kept, since registering one by hand is the only way to supply a template in the browser.teddy.setCacheTemplates(true)when instantiating Teddy, or passcache: truein the model on each render.teddy.setCacheTemplates(boolean)to control the above, and support for acacheoption in the model, which takes precedence over both that setter and Express'sview cache.teddy.clearTemplates()to now clear the templates that were read from the filesystem, not just the ones registered by hand.<include>resolving its partial through the template registry rather than through the loader, which meant an included template could not be re-read after it changed.<p if-a true='class="x"' if-b true='data-y="z"'>now applies both outcomes.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.