HTML tree view

What problem are we solving?

Some formats, like Maven and Raw, have built-in hierarchy that we’ve flattened in the NXRM3 browse UI, resulting in information loss. Also, flat formats (e.g. Docker, NuGet, NPM) risk introducing performance issues, since everything exists at the same directory level (yes, you can page instead, but this ignores the usability concerns of browsing a flat list containing 100k+ entries).

How will we measure success?

There are currently 24 votes across the two sister issues (NEXUS-12518 and NEXUS-12531). We will validate our improvements with everyone who voted. If successful, 90%+ of the people we talk to will indicate that our solution addresses their needs.

What do we need to do?

We’ll start by building a tree browsing service that can feed both of our user facing views ([HTML|PE-51] and Ext JS). This service will build sensible hierarchies for each of our supported formats, and introduce hierarchy where appropriate to aid performance and usability (e.g. translating dots in package names to namespaces).

Once the service has been built, we’ll create a simple HTML view that we can demo and potentially expose to users as a simple API. We’ll be keying our HTML views off of what NXRM2 does for Maven repositories.