We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This enables a much easier way to understand how or why a pattern was introduced. For instance, you can answer questions such as:
solmate
open-zeppelin
To query the codebase to search for such a pattern, we can specify an AST selector as it would be accepted by Forge Lint.
AST selector is supported on AST Explorer for solidity.
For instance, to search for console.log() calls in javascript, the ESLint selector would be
"CallExpression[callee.object.name=console][callee.property.name=log]"
This could be used to help automate refactoring, finding regressions, and more since the debugger is based on a typed AST.
see ref. implementation for ESLint, https://github.com/NickHeiner/query-pattern-age/tree/use-in-tv#query-pattern-age
The text was updated successfully, but these errors were encountered:
Is this report meant to be subimtted to the solc-typed-ast repo?
Sorry, something went wrong.
Imma be real with you i opened this issue as a way to reference the idea - bookmark it for myself
Really why not just go to yul ir that would be better
Could you provide more context about what you mean by "going to yul ir" in the context of the solidity debugger?
No branches or pull requests
AST Query
TLDR: Provide an AST pattern, and see details about when that pattern was introduced.
Overview
This enables a much easier way to understand how or why a pattern was introduced. For instance, you can answer questions such as:
solmate
, and which are usingopen-zeppelin
?To query the codebase to search for such a pattern, we can specify an AST selector as it would be accepted by Forge Lint.
For instance, to search for console.log() calls in javascript, the ESLint selector would be
"CallExpression[callee.object.name=console][callee.property.name=log]"
Other use cases
This could be used to help automate refactoring, finding regressions, and more since the debugger is based on a typed AST.
References
see ref. implementation for ESLint, https://github.com/NickHeiner/query-pattern-age/tree/use-in-tv#query-pattern-age
The text was updated successfully, but these errors were encountered: