fix(weave_query): Ensure newVars are passed in when expanding a panel op #3059
+12
−6
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.
Description
The panel op,
.table()
crashes the panel when it is used in the following manner:runs.summary["table"].run.table
runs.summary["table"].table.run.table
The error occurs from a var node being sent to the query engine service. After much debugging and pairing on this with @shawnlewis, we determined that the
useExpandedNode
hook was not receiving the frame with theruns
node, so the solution was to pass innewVars
from theusePanelExpressionState
hook.No longer crashes:
Testing
How was this PR tested?