Feature description or problem with existing feature
We have some projects where many namespaces share a common base.
Nowadays we add the complete use and then invoke only class.
This sometimes causes us a collision of namespaces.
Describe the solution you'd like
It would be interesting to be able to define a common base and if it detects it, use it to import the classes.
Additional context
This would solve the problem that if there is another class with the same name in another namespace it would be necessary to use aliases and at the same time reduce the number of use lines.
Feature description or problem with existing feature We have some projects where many namespaces share a common base. Nowadays we add the complete use and then invoke only class.
This sometimes causes us a collision of namespaces.
Describe the solution you'd like It would be interesting to be able to define a common base and if it detects it, use it to import the classes.
For example, we have the following classes:
If we define the following use:
use App\Services\Integrations;When they are imported it would have to do it in the following way
Additional context This would solve the problem that if there is another class with the same name in another namespace it would be necessary to use aliases and at the same time reduce the number of
uselines.