Skip to content

Strange behavior of 0.5.4 for ComposerFinder::inNamespace #24

Closed as not planned
@andrew-demb

Description

@andrew-demb

I'm in the process of making graphqlite-bundle compatible with graphqlite v7 (dev) and symfony v7
(continuation from PR thecodingmachine/graphqlite-bundle#203; here's a permalink to the used graphqlite dependency version https://github.com/thecodingmachine/graphqlite/tree/0f1a112fe46a131fb6564b2f1001b5dc6d35b075)

While investigating issues with test suite I found, that ComposerFinder::inNamespace does autoload of unrelated classes (not related to the requested namespace).

image

image

Please suggest a path to investigate the reason for such behavior and how to fix it (should it be a fix in class-finder or in graphqlite?)


The reason, why I am investigating it - is because of that behavior - in graphqlite-bundle tests there's an error about redeclaring an existent class.

image

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