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
{{ message }}
Repository navigation
Commit d6175bb
Browse filesBrowse the repository at this point in the historyBrowse files
fix: Resolve the package of class/module symbols from the declaring file
typeToSymbol resolved the package of a class or module type with
getPackageInfo(node, ...), which classifies by the file containing the
reference. Every reference emitted while visiting a project file is in
the project, so any class reached through an alias declaration
(`pkg.Thing`, or `Thing` re-exported from a submodule) was emitted under
the project package instead of the package that declares it. Functions
already used guessPackage(decl.moduleName, decl.path) and were correct.
Use guessPackage with the type's own moduleName and filePath for classes,
modules and TypeVar bounds, falling back to a local symbol when the
package is unknown, as getFunctionSymbol does.
Adds a snapshot test with a fake `widgets` package exposed through
extraPaths and listed in testEnv.json, so references to classes
re-exported from a submodule are checked against the dependency's
package.
0 commit comments