feature question: infer a function def for a call about libcst HOT 5 CLOSED

@zhammer Retrieve the FunctionDef node given a Call is doable through our Scope metadata provider.
https://2589-200896124-gh.circle-artifacts.com/0/doc/metadata.html#libcst.metadata.Scope

You can add the dependency to use the provider in your visitor/transformer

class MyVisitor(libcst.CSTVisitor):
    METADATA_DEPENDENCIES = (libcst.metadata.ScopeProvider,)

    def visit_Call(self, node):
        scope = self. get_metadata(libcst.metadata.ScopeProvider, node)
        assignments = scope[node.func.value]  # you'll get a list of possible assignments

See the Assignment class for more detail.
https://2580-200896124-gh.circle-artifacts.com/0/doc/metadata.html#libcst.metadata.Assignment

I'm working on a couple more powerful metadata providers and plan to add tutorial to demonstrate some use cases.

Currently the metadata providers only analyze one single module and single module is the scope of LibCST. For collecting metadata across multiple files, we plan to work on it in the future by adding another layer on top of LibCST to support code repository scope analysis/refactoring.

from libcst.

hey @jimmylai ! any updates on the repository analysis/refactoring? just curious

from libcst.

@zhammer I'm currently working on it and hoping to deliver it by the end of this month.

from libcst.

Update: the TypeInferenceProvider PRs are in review and will be published in the next release.
#159
#179

from libcst.

TypeInferenceProvider is available in LibCST 0.2.6. Given a Call.func, it provides the type annotation of the node (Callable(name)[...]). The name is provided as a fully qualified name. So we can potentially use the name to read source code and parse as CST to get the FunctionDef node.

from libcst.