Skip to content

Support workspaces with identically named packages #41

@sprocter

Description

@sprocter

As part of #38, some semi-hacky code was introduced that may cause errors if there are packages with the same name in the workspace (see @lwrage's comment in that thread). That should be fixed, but it's not worth delaying the merge, so I'm going to accept the pull.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions