Skip to content

Uniqueness on final package list is not enforced #8

@sveetch

Description

@sveetch

Currently if the requirements contains the same package multiple time, it is not reduced with only unique packages, the multiple ones are still processed from analyzer and stored.

Identical package names with identical specifier could be reduced to a single one, however for identical packages with different identifier it is still to know what to do exactly.

Keeping multiple identical packages may pollute the report and more important it performs a API request for each ones.

Finally, multiple identical packages should emit a warning, even if it is ignored in analyzer the user must know it have duplicates.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions