{"version":"2.1.269","anchor":"cel-comprehension-macro-bug-fix-error-checks-were-on-the-wr","canonical_anchor":"cel-comprehension-macro-bug-fix-error-checks-were-on-the-wr","heading":"CEL comprehension macro bug fix: error checks were on the wrong variable","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/cel-comprehension-macro-bug-fix-error-checks-were-on-the-wr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### CEL comprehension macro bug fix: error checks were on the wrong variable\n\nFixed a bug where CEL comprehension expressions could silently swallow evaluation errors\n\n**What**\n\nClaude Code uses CEL (Common Expression Language) internally to evaluate list and map comprehensions, the kind of expression used to loop over or filter a collection. Several checks that were supposed to detect evaluation errors were accidentally checking the wrong variable, a leftover from earlier code minification, instead of the value that had actually just been computed. This has been fixed so the error checks now test the right value.\n\n**Why**\n\nBefore this fix, an error occurring inside a `for`- or `filter`-style comprehension could go undetected and be treated as if evaluation had succeeded, potentially producing incorrect results (such as a type mismatch between an iterable and a non-iterable) without surfacing the underlying error.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}