Skip to content

[FEATURE]: Use a stack of dependency resolvers #1421

@ericvergnaud

Description

@ericvergnaud

Is there an existing issue for this?

  • I have searched the existing issues

Problem statement

As we expand the scope of source code components being assessed, resolving names becomes more and more complex and fragile.

Proposed Solution

Use a stack of specialised dependency resolvers such that the contextual logic remains simple.

Additional Context

sub-ticket of #1202

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomersmigrate/codeAbstract Syntax Trees and other dark magicmigrate/pythonPull requests that update Python code

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions