Skip to content

fix: correctly identify variable access as INDIRECT if accessed after a fact#1697

Merged
triceo merged 1 commit into
TimefoldAI:mainfrom
Christopher-Chianelli:fix/indirect-parent-variable-type
Jul 11, 2025
Merged

fix: correctly identify variable access as INDIRECT if accessed after a fact#1697
triceo merged 1 commit into
TimefoldAI:mainfrom
Christopher-Chianelli:fix/indirect-parent-variable-type

Conversation

@Christopher-Chianelli

Copy link
Copy Markdown
Contributor

The path "fact.variable" was incorrectly identified as "NO_PARENT" instead of "INDIRECT". This can cause an unsuitable graph structure to be used, causing score corruption.

Fixes #1696

… a fact

The path "fact.variable" was incorrectly identified as "NO_PARENT"
instead of "INDIRECT". This can cause an unsuitable graph structure
to be used, causing score corruption.
@sonarqubecloud

Copy link
Copy Markdown

@triceo triceo merged commit 471ecca into TimefoldAI:main Jul 11, 2025
34 checks passed
@Christopher-Chianelli Christopher-Chianelli deleted the fix/indirect-parent-variable-type branch May 14, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unexpected score corruption when adding (but not using) a second declarative shadow variable

2 participants