Like they won't really conflict with each other. If it's a .drv file there's not much of a tree to explore. If it's not a .drv file then we can just hide the drv data tables etc. It's just less mental work for the user not to have to choose in advance whether they want to explore the .nar tree or the .drv specifications.
See the different pages in db.html, drv.html, and nar.html.
Actually is the file name enough to determine which to do? How does the Nix CLI know what you mean when it's ambiguous?
Like they won't really conflict with each other. If it's a .drv file there's not much of a tree to explore. If it's not a .drv file then we can just hide the drv data tables etc. It's just less mental work for the user not to have to choose in advance whether they want to explore the .nar tree or the .drv specifications.
See the different pages in db.html, drv.html, and nar.html.
Actually is the file name enough to determine which to do? How does the Nix CLI know what you mean when it's ambiguous?