Skip to content

Raise Errors on parseable but nonsensical MatchSpecs #13

Description

@remkade

Its possible to create a MatchSpec that is valid but nonsensical. Lets error out and give a helpful message in those cases.

Examples

Here's a few examples that would be parseable, but don't really make any sense.

# Package name matches everything:
*

# Channel shouldn't be globbable, its dangerous. Might be useful on searching though?
conda-*/python

# Certain keys don't make sense to allow partial globs
[sha256="abcd*" md5="abc*"]

# Questionable, maybe encourage people to omit key/values that already default to matching everything?
[license="*"]

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions