Skip to content

FQN collisions with class and type for example #61

@fuhrmanator

Description

@fuhrmanator

Declaring a class can also declare a type. So the FQN that has {blah.ts}.MyClass is ambiguous.

We added [Node.getKindName()] which helps a little, but unfortunately a Famix.Type and Famix.Class are created from the same node, ClassDeclaration, so it doesn't work to use Node.kind.

Another option is to add the Famix.Element context.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions