Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-17648

npm components shown as assets

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.13.0
    • Fix Version/s: None
    • Component/s: Browse Storage, NPM
    • Labels:
    • Story Points:
      2

      Description

      While testing cleanup I was looking at the attached screen and reflected that this might be very confusing for users trying to figure out what they delete.
      Cleanup states (and does) that we look at the parts of the asset (for npm, it's just the tgz) and based on them delete the component.
      However, looking at this screen, it seems easy to think that if testproject1-0.0.1 asset was to be removed it'd remove the "component" parent of testproject which is not the case.

      To help clarify this, we suggest that the button instead of delete asset say delete component (also true in the case of npm).

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Maksym Kalachov Maksym Kalachov
            Team:
            NXRM - Mad Max
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title