You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add debug logging to MissingResultTypeSpecifierCorrector
Enhanced logging to improve traceability of corrections for missing `resultTypeSpecifier` values in `Query`, `ReturnClause`, and `Tuple` nodes.
- Added logs for `Query` nodes to indicate when `ReturnClause.resultTypeSpecifier` is set to the `elementType` of a `ListTypeSpecifier`.
- Added logs for `ReturnClause` nodes to indicate when `Tuple.resultTypeSpecifier` is set to the `TupleTypeSpecifier`.
- Added logs for `Tuple` nodes to indicate when missing `Tuple.element.value.resultTypeSpecifier` values are set from the `TupleTypeSpecifier`.
These changes provide additional context, such as `locator` and `expressionKey`, to aid debugging.
"Setting missing Tuple.resultTypeSpecifier to TupleTypeSpecifier to '{resultType}' on ReturnClause @ {locator}.\n{expressionKey}",
63
+
tupleTypeSpecifier,
64
+
clause.locator,
65
+
self.ContextStackString);
56
66
tuple.resultTypeSpecifier=tupleTypeSpecifier;
57
67
}
58
68
}
59
69
60
70
{
61
71
// If a Tuple has elements with missing resultTypeSpecifier but the Tuple itself has a TupleTypeSpecifier as resultTypeSpecifier, set the missing element resultTypeSpecifiers from the TupleTypeSpecifier
0 commit comments