Skip to content

Bad results when scanning code using traits #19

@ahungry

Description

@ahungry

I ran the analyzer against a code base that makes extensive use of traits. In almost all the cases these trait files return errors stating references to undefined properties/constants etc., as these are defined in classes which invoke the trait.

Is it possible to fix this so that when a trait is being analyzed, it is analyzed in context of the class that is using the trait? (so, if you have 1 trait re-used in 3 distinct classes, that would be 3 analysis for the trait - 1 for each class/trait pairing).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions