Skip to content

Conversation

nathanskone
Copy link

Resolves #10157

DRAFT: Just reproduces the bug, does not resolve it yet

Problem

Unit tests fail with a compilation error claiming a macro is “undefined” (even though it exists), triggered when combining macro calls in expressions.

Solution

???

Checklist

  • I have read the contributing guide and understand what's expected of me.
  • I have run this code in development, and it appears to resolve the stated issue.
  • This PR includes tests, or tests are not required or relevant for this PR.
  • This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
  • This PR includes type annotations for new and modified functions.

@cla-bot cla-bot bot added the cla:yes label Oct 11, 2025
@nathanskone nathanskone changed the title Adding unit test that reproduces macro composition failure in unit tests Fix: macro composition in unit tests Oct 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Unit test raising error '<macro name>' is undefined. This can happen when calling a macro that does not exist.

1 participant