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
Importas uses rules to standardize package aliases. But as the project gets bigger, there will be more and more rules and it is difficult to maintain. There may be cases where the same package has different aliases because this package is not covered by the rules. Importas cannot handle this situation because it does not support checking whether there are different aliases for the same package in different go files or in same go file without rules.
solution you'd like.
Checking whether there are different aliases for the same package before checking the aliases according to the importas rules.
Like this :
Problem:
Importas uses rules to standardize package aliases. But as the project gets bigger, there will be more and more rules and it is difficult to maintain. There may be cases where the same package has different aliases because this package is not covered by the rules. Importas cannot handle this situation because it does not support checking whether there are different aliases for the same package in different go files or in same go file without rules.
solution you'd like.
Checking whether there are different aliases for the same package before checking the aliases according to the importas rules.
Like this :
This little implement, https://github.com/Rodge0/samealias, maybe useful.
Appreciate!
The text was updated successfully, but these errors were encountered: