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
bug(cli/mcp): find_importers reads module.alias but the alias is stored on the IMPORTS relationship, so import_alias is always null #1515
Module nodes are never written with an alias property, so module.alias evaluates to null on every row. Note the relationship is already bound as imp in the same pattern — the data is right there.
Impact
The find_importers MCP tool reports import_alias: null for every result, including import numpy as np where the alias is the whole point of the query. An agent asking "what name is this module imported under here?" gets nothing back and has no way to tell that the field is broken rather than genuinely absent.
Cross-linking: this shares a root cause with item 3 of #1533 (the C++ toolkit reads m.alias in query_tool_languages/cpp_toolkit.py:46).
In both places the alias is read off the Modulenode, but writer.py:580-598 only ever writes it to the IMPORTSrelationship:
MATCH (m:Module) RETURN count(m), count(m.alias) -> 160, 0
MATCH ()-[i:IMPORTS]->() RETURN count(i), count(i.alias) -> 249, 249
Whoever picks either one should fix both call sites together — the change is m.alias → i.alias in each. A repo-wide grep for .alias against Module patterns would be worth doing at the same time in case there is a third.
Activity
github-actions commentedon Aug 1, 2026
Hi! 👋 Join our CodeGraphContext Discord channel to collaborate: https://discord.gg/dR4QY32uYQ
Shashankss1205 commentedon Aug 1, 2026
Cross-linking: this shares a root cause with item 3 of #1533 (the C++ toolkit reads
m.aliasinquery_tool_languages/cpp_toolkit.py:46).In both places the alias is read off the
Modulenode, butwriter.py:580-598only ever writes it to theIMPORTSrelationship:Whoever picks either one should fix both call sites together — the change is
m.alias→i.aliasin each. A repo-wide grep for.aliasagainstModulepatterns would be worth doing at the same time in case there is a third.chore(release): bump version to 0.5.5 (#1569)