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
When an import is specified using a path without an alias given, the package identifier assigned to that import is expected to be the single package seen in source files in that location. Currently GoWorks assumes that the package name and the folder name are the same, but this is not always the case.
💡 A workaround when this occurs is to explicitly assign an alias to the import which happens to match the true name of the package:
When an import is specified using a path without an alias given, the package identifier assigned to that import is expected to be the single package seen in source files in that location. Currently GoWorks assumes that the package name and the folder name are the same, but this is not always the case.
💡 A workaround when this occurs is to explicitly assign an alias to the import which happens to match the true name of the package:
The text was updated successfully, but these errors were encountered: