Nagato-Yuzuru/predylogic - CodSpeed

predylogic

Blog Docs Changelog

Performance History

Latest Results

Potential fix for code scanning alert no. 5: Workflow does not contain permissions (#47) Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

main

3 days ago

Potential fix for code scanning alert no. 5: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

alert-autofix-5

3 days ago

Potential fix for code scanning alert no. 5: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

alert-autofix-5

3 days ago

fix(schema)!: separate rule_def_name discriminator from rule parameters Closes #43 --- * test(schema): expose rule_def_name namespace collision Adds a regression test registering a rule whose signature has a parameter named `rule_def_name`. Currently fails with `TypeError: got multiple values for keyword argument 'rule_def_name'` from `create_model`, since the discriminator and rule parameters share the same kwargs namespace. * test(engine): expose *args/**kwargs manifest round-trip failure * fix(schema): nest rule params under BaseRuleConfig.params * docs(quick-start): migrate examples to nested params shape * fix(engine): surface VAR_KEYWORD vs KEYWORD_ONLY key collision --- BREAKING CHANGE: manifest JSON moved user parameters under a dedicated `params` sub-object. Payloads authored against the old flat format must migrate: { "rule_def_name": "is_adult", - "min_age": 18 + "params": { + "min_age": 18 + } } Rules with no required parameters may omit `"params"`; rules with required parameters must supply `"params": {...}` explicitly. The `x-params-order` JSON-schema annotation is removed — order is carried structurally by the `<Name>Params` sub-model.

main

3 days ago

fix(engine): surface VAR_KEYWORD vs KEYWORD_ONLY key collision

fix/schema-dedup

3 days ago

docs(quick-start): migrate examples to nested params shape

fix/schema-dedup

3 days ago

fix(trace): flat N-ary trace trees with correct child order (#42) * test: add comprehensive test suite for Trace observability mechanism * test: enhance trace shape assertions for improved clarity and structure * fix(trace): produce flat N-ary trace trees with correct child order Resolves issue #38. Four related fixes in the predicate compiler and trace rendering so `all_of([A, B, C])` and `A & B & C` both yield a flat AND node with three children in left-to-right order: - `_collect_chain` N-ary branch now reverses `children[1:]` so the LIFO stack push restores left-to-right evaluation order (was `[B, C, A]`, now `[C, B, A]`). - FLATTENED marker count now reflects the walked chain length instead of the top-level `len(children)`. Previously, binary-chained operators (`A & B & C`) would silently drop the first leaf because the chain walked through same-type descendants. - `_rt_and` / `_rt_or` build a single N-ary `Trace` directly instead of accumulating via `Trace.__and__` / `__or__`, which produced nested binary trees. Short-circuit paths still return only the children that were actually evaluated. - `DefaultTraceStyle.render` falls back to `node.name` when `node.desc` is missing so leaves render their identifier instead of `LEAF`.

main

4 days ago

fix(trace): produce flat N-ary trace trees with correct child order Resolves issue #38. Four related fixes in the predicate compiler and trace rendering so `all_of([A, B, C])` and `A & B & C` both yield a flat AND node with three children in left-to-right order: - `_collect_chain` N-ary branch now reverses `children[1:]` so the LIFO stack push restores left-to-right evaluation order (was `[B, C, A]`, now `[C, B, A]`). - FLATTENED marker count now reflects the walked chain length instead of the top-level `len(children)`. Previously, binary-chained operators (`A & B & C`) would silently drop the first leaf because the chain walked through same-type descendants. - `_rt_and` / `_rt_or` build a single N-ary `Trace` directly instead of accumulating via `Trace.__and__` / `__or__`, which produced nested binary trees. Short-circuit paths still return only the children that were actually evaluated. - `DefaultTraceStyle.render` falls back to `node.name` when `node.desc` is missing so leaves render their identifier instead of `LEAF`.

trace/test-suite

4 days ago

Latest Branches

0%

Potential fix for code scanning alert no. 5: Workflow does not contain permissions#47

3 days ago

4bf5089

alert-autofix-5

0%

Fix/schema dedup#45

3 days ago

586325e

fix/schema-dedup

0%

fix(trace): flat N-ary trace trees with correct child order#42

4 days ago

0d2c155

trace/test-suite

© 2026 CodSpeed Technology

Home Terms Privacy Docs