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
This is a proposal to introduce a refactoring to remove using, i.e. all the types from the used namespace would get fully qualified (or as needed regarding to other imported namespaces).
Background and Motivation
Namespaces refactoring can lead to this operation. Another use case is trying to use a type conflicting with one currently used but from different namespace. You cannot use both namespaces but you don't want to favoritize any.
Summary
This is a proposal to introduce a refactoring to remove using, i.e. all the types from the used namespace would get fully qualified (or as needed regarding to other imported namespaces).
Background and Motivation
Namespaces refactoring can lead to this operation. Another use case is trying to use a type conflicting with one currently used but from different namespace. You cannot use both namespaces but you don't want to favoritize any.
Proposed Feature
Setup:
Before refactoring:
After refactoring to remove
using MyNamespace.Area1
:Now
class Boo : Area2.MyClass
can be added without conflict.Note that this is difficult to do manually because "fully qualify" quick fix cannot be applied file-wise.
The text was updated successfully, but these errors were encountered: