Skip to content

no-extra-aliases is problematic in larger codebase #29

@fingon

Description

@fingon

Forbidding extra aliases when the import names do not conflict is what I want. But defining and maintaining aliases for package names that are unique for whole codebase as it grows feels like a chore (and not necessarily the intent).

Example (our use case): In our monorepo, we have lots of protobufs. And they're colocated with their packages, e.g. pkg/foo/proto, pkg/bar/proto, etc (in separate subdirectory due to code generation dependency reasons). Without defining all aliases (fooproto, barproto, etc), the no-extra-aliases cannot work for code which refers to more than one /proto (as it changes all imports to 'proto' which then conflict and fail to compile), but on the other hand it would be nice to use it elsewhere without such naming conflict resolution going on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions