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 has been archived by the owner on Jan 16, 2021. It is now read-only.
Code example that use named import paths can render the code confusing because it is unclear to the reader which package the import refers to. Regardless of whether these are considered an anti-pattern or not, it's a valid use case and it would be helpful to cover for.
Code example that use named import paths can render the code confusing because it is unclear to the reader which package the import refers to. Regardless of whether these are considered an anti-pattern or not, it's a valid use case and it would be helpful to cover for.
Example documentation with the problem: https://godoc.org/gopkg.in/DataDog/dd-trace-go.v1/contrib/gorilla/mux.
A possible solution would be:
Where this would be shown only for named imports.
The text was updated successfully, but these errors were encountered: