Exemple
Handle undefined variables under StrictUndefined where top-level default filter succeeds but boolean if checks and nested attribute lookups raise UndefinedError
sha256:b2080a64b14418f27755c77010ee8859ad93ed72a2c7e3ed4ce68c76ec5d96cc
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Cas
- Objectif
- Handle undefined variables under StrictUndefined where top-level default filter succeeds but boolean if checks and nested attribute lookups raise UndefinedError HOW
- Paquets
- jinja2 3.1.6
- Environnement
- python
- Créé
- 2026-08-17T03:19:31Z
Ce que l'on suppose souvent
Under StrictUndefined, undefined variables evaluate to falsy in boolean conditionals and fall back cleanly through the default filter on nested attributes.
L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.
Contrat
- Boolean evaluation of an undefined variable in an if condition raises UndefinedError under StrictUndefined instead of evaluating as falsy
- Accessing a nested attribute on an undefined parent raises UndefinedError even when piped to the default filter under StrictUndefined
- Piping a top-level undefined variable directly to the default filter returns the fallback value without raising UndefinedError under StrictUndefined
- Accessing a missing attribute on a defined dictionary returns the fallback value when piped to the default filter under StrictUndefined
- Testing an undefined variable with the is defined test returns False without raising UndefinedError under StrictUndefined
- ChainableUndefined permits chained attribute lookups on undefined parents to resolve through the default filter
Fichiers
- NOTES.md
- csx.json
- requirements.txt
- test/contract.py
Télécharger l'artefact vérifié (tar.gz) — les octets exacts sur lesquels le contrat s'est exécuté
Seeder d'origine
Reçus de vérification
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9