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
Is your feature request related to a problem? Please describe.
For Ruby, we have two views of the AST: The rich AST, and the desugared AST. The AST viewer (that is, the underlying ide-contextual-queries/print-ast query) displays the former, but sometimes it would be nice to see the desugared view.
Describe the solution you'd like
Add a drop-down to the AST viewer where one can select among multiple ide-contextual-queries/print-ast queries (when multiple queries are present).
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Perhaps this isn't possible, but could you always return both asts? They could be created as two top level nodes and the user would be able to see both at the same time.
Perhaps this isn't possible, but could you always return both asts? They could be created as two top level nodes and the user would be able to see both at the same time.
In this case the output would not be a tree, as some AST nodes would appear in both trees, and I am not sure that the viewer handles that well (and the test output, where we use @kind graph certainly doesn't). As a user, I also think it would be weird to have the same element appear multiple times; which one should we jump to, when selecting some code?
Is your feature request related to a problem? Please describe.
For Ruby, we have two views of the AST: The rich AST, and the desugared AST. The AST viewer (that is, the underlying
ide-contextual-queries/print-ast
query) displays the former, but sometimes it would be nice to see the desugared view.Describe the solution you'd like
Add a drop-down to the AST viewer where one can select among multiple
ide-contextual-queries/print-ast
queries (when multiple queries are present).Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: