Repository navigation

Issues

New issue

A decimal("…") literal passed as an argument to a def temporal macro is rejected as "unknown macro decimal"
dogwood-policy/dogwood#33 · opened on Nov 2, 2026
A def temporal macro whose whole body is tp(?t) is rejected as "macro-in-macro is not supported"
dogwood-policy/dogwood#32 · opened on Nov 2, 2026
Provider record field names that are not Cedar identifiers ("a b", "x-y", "if") are written unquoted into a synthesized schema, so lowering fails
dogwood-policy/dogwood#31 · opened on Nov 2, 2026
Nested previous under the default pinned event schema takes time polynomial in the number of in-window events, with the degree growing with nesting depth
dogwood-policy/dogwood#30 · opened on Nov 2, 2026
Nested positive-left since under the default pinned event schema takes time polynomial in the number of in-window events, with the degree growing with nesting depth
dogwood-policy/dogwood#29 · opened on Nov 2, 2026
dogwood explain does not parenthesize an if that is an operand of &&/||, so two policies with different verdicts get identical prose
dogwood-policy/dogwood#27 · opened on Nov 2, 2026
1
dogwood explain prints context has input.user and context has "input.user" as the same text, but the two conditions decide differently
dogwood-policy/dogwood#26 · opened on Nov 2, 2026
1
ParsedPolicy::expanded_source renders !(-3) as !-3, which Dogwood's parser rejects
dogwood-policy/dogwood#25 · opened on Nov 2, 2026
ParsedPolicy::expanded_source renders -(-3) as --3, which re-parses to the literal 3
dogwood-policy/dogwood#24 · opened on Nov 2, 2026
dogwood validate drops the input/output fields of an action whose context names a top-level common type from inside a namespace
dogwood-policy/dogwood#23 · opened on Nov 2, 2026
Temporal validator types a bound variable by the last same-named binder in the condition, not the binder in scope
dogwood-policy/dogwood#22 · opened on Nov 2, 2026
count/sum rejected with "for-variable does not occur in the aggregation body" when the variable is used only inside a temporal macro call
dogwood-policy/dogwood#21 · opened on Nov 2, 2026

Navigation Menu

Repository navigation

Issues

Issues

A `decimal("…")` literal passed as an argument to a `def temporal` macro is rejected as "unknown macro `decimal`"

A `def temporal` macro whose whole body is `tp(?t)` is rejected as "macro-in-macro is not supported"

Provider record field names that are not Cedar identifiers ("a b", "x-y", "if") are written unquoted into a synthesized schema, so lowering fails

Nested `previous` under the default pinned event schema takes time polynomial in the number of in-window events, with the degree growing with nesting depth

Nested positive-left `since` under the default pinned event schema takes time polynomial in the number of in-window events, with the degree growing with nesting depth

`dogwood explain` does not parenthesize an `if` that is an operand of `&&`/`||`, so two policies with different verdicts get identical prose

`dogwood explain` prints `context has input.user` and `context has "input.user"` as the same text, but the two conditions decide differently

`ParsedPolicy::expanded_source` renders `!(-3)` as `!-3`, which Dogwood's parser rejects

`ParsedPolicy::expanded_source` renders `-(-3)` as `--3`, which re-parses to the literal `3`

`dogwood validate` drops the input/output fields of an action whose context names a top-level common type from inside a namespace

Temporal validator types a bound variable by the last same-named binder in the condition, not the binder in scope

`count`/`sum` rejected with "`for`-variable does not occur in the aggregation body" when the variable is used only inside a temporal macro call