Handle nested UDF calls during import migration #12575
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #12542
The logic that replaces references in imported types, variables, and functions is not currently handling UDF calls within UDF calls, e.g.,
In the definition of
bar
, the outerfoo
call would be migrated (i.e., it would refer to a UDF in a closure namespace (_1.foo
)), but the innerfoo
call would not (i.e., it would refer to a UDF in the__bicep
namespace). The compiled expression would end up looking something like"[_1.foo(__bicep.foo(parameters('input')))]"
, which will fail to evaluate at runtime.Microsoft Reviewers: Open in CodeFlow