Skip to content

Support ethpm URIs without specified package versions #89

@njgheorghita

Description

@njgheorghita

What was wrong?

The cli supports ethpm URIs like...
ethpm://ens.packages.eth : specify only a registry
ethpm://ens.packages.eth/[email protected] : specify a package release on a registry
ethpm://ens.packages.eth/[email protected]/deployments/Token: specify a certain asset within a package

From a UX point of view it would be nice to support
ethpm://ens.packages.eth/package - rather than requiring a version to be specified.

Since ethpm does not enforce semver, if this kind of uri is used - then a list of all detected versions should be printed - giving the user the chance to choose what version they want to install/activate (similar to how this is handled in ethpm update).

How can it be fixed?

  • parse_registry_uri in web3.py will need to be updated. currently if an ethpm uri contains a package name a version is also required.
  • an input() prompt will be required for both ethpm activate and ethpm install that allows the user to specify a version from a list of available versions (similar to ethpm update)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions