The functionality for adding did open is nice, but when running did init, it's not evident that that's why the user can specify the install directory of did.
This together with the issue of folder traversal, as you can't navigate up in the file structure to find the did-folder, makes the user think they're somehow botching the init-process.
proposed solution
- enable upwards folder traversal in the file structure picker (if possible)
- describe why we're asking the user for the location of their did-installation OR
- move or remove the registration of the
did open feature. Maybe trigger the "where is your did installation?" the first time you run did open?