Bug 13277 – The base class in the JSON output is always unqualified
Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P1
Component
dmd
Product
D
Version
D2
Platform
All
OS
All
Creation time
2014-08-10T17:48:00Z
Last change time
2014-08-17T04:43:13Z
Keywords
pull
Assigned to
nobody
Creator
blah38621
Comments
Comment #0 by blah38621 — 2014-08-10T17:48:34Z
Currently in the JSON DMD produces, the "base" property of a "class" node is
always the unqualified name of the base class. This means that, in order to
determine what class that property is actually referencing, you have to
determine what modules are imported at the location the class is declared, as
well as have access to a JSON file generated for those modules, and then search
those imported modules, dealing with selective imports, alias imports, and
public imports as well. This is way more work that should be needed. I instead
propose that the "base" property should contain the qualified name of the base
class, which would require much less work to resolve, as it would be possible
to resolve that name in a direct top-down approach rather than a very indirect
inside out approach.