Fix call tag variable assignments using Proxy-based context #181
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.
The
calltag was not updating exported scene variables. Assignments like<call method="hoge = 1" />created local variables instead of modifying the scene context, breaking conditional logic and variable expansion.Root Cause
executeCode()passed scene properties by value, making assignments local-only:Changes
executeCode()to use Proxy: Intercepts property access/assignment to modifysceneFiledirectlywithstatement: Enables natural variable syntax while maintaining reference to source objectVerification
Manual test confirms proper behavior:
Variable assignments now propagate correctly to conditionals (
if="hoge==1") and expansions ({{hoge}}).Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.