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 }}
This repository was archived by the owner on Jan 31, 2022. It is now read-only.
you are adding use statements, but without checking if they could conflict with other classes in the same namespace (possible only if the user try to typehint a class ...\Base* as all om classes start with this prefix though) or with other use statement (more likely).
I see 2 possible ways to fix it:
don't generate a use statement, using the FQCN in the method signature => no conflict ever, but ugly generated code
alias the use statement to ensure the uniqueness => conflict possible if the logic choosing the alias is bad, ugliness possible depending of the generated alias
you are adding use statements, but without checking if they could conflict with other classes in the same namespace (possible only if the user try to typehint a class
...\Base*as allomclasses start with this prefix though) or with other use statement (more likely).I see 2 possible ways to fix it: