Arvados

Some comments:

• I think it would be really nice to make smaller sized commits in the future, for readability reasons. I appreciate the detailed descriptions on these but it's a lot easier to follow (at least, for me) having bite sized commits instead of just a couple commits with all the changes.
• Changes at src/store/tree-picker/tree-picker-actions.ts might require some unit testing.
• It would be good to have unit tests for the changes made in src/models/tree.ts too.
• In tree-picker-actions.ts the error message "Some selections failed to load and were removed" may be a bit confusing to the user, do you think it would be worth explaining which selections were skipped on the console (and inform the user about that) or in some other way?
• When editing a multi-dir input field and expanding a group, I get a checkbox beside the group but it doesn't do anything when clicking on it (see attached video)
  • OK, I realize this bug report is out of scope, so maybe we should make a different ticket for it.
• When editing a multi-dir input field, the chips added to the bottom only display the dir name, I think it would be super helpful to have some kind of tooltip on each that shows its full tree path or some other data that provides some context data. I think this would be useful for selections on extremely long list of projects, especially when there're equally named subdirs.
  • This also may be an out of scope bug, feel free to delegate it to a different ticket.
• Question: Is there already a consensus about what to do when selecting a parent dir and a subdir at the same time? Right now the UI treats them as different selections.
• Can we have a Cypress test exercising these new behaviors?

Changes at arvados-workbench2|162665e037ec2de3203e8ed34991b1f443462382
Tests: (jekins still broken so local run log attached)

• Add unit testing for tree picker initialization / loadInitialValue actions
• Add unit tests for new tree method
• Improved error handling
  • Catch errors in tree picker loadProject and show toast + console error with rejection reason
  • Trigger rejected promise if ancestor service returns no ancestors, add console.error to note uuid of item that failed to preselect
• Added cypress test to test subdirectory selection and reselection when reopening picker
• There is currently no consensus on how to handle selecting a parent and child directory node in the tree picker because before now, the only occurrences of multi select tree picker are in situations where the parent and child must be different types (with the exception of a multi project picker with nested projects, which I don't think is done anywhere but could be a problem with the previous scheme), thus the picker which should only accept 1 type ignores the parent selection in the setvalue handler (eg a multi collection picker where selecting a project selects all collections within without including the project as a selection despite being selected). The default behavior before was to always select all selectable child nodes when a parent is selected and to limit what can be selected by only loading the desired item types. It also enforced that selecting all selectable child items causes the parent to be selected too. Enabling collection subdirectory picking changes this since now both a parent and child can be a valid selection type, and will both validate as a selected location - so I disabled the cascade selection up/down behavior so that you can select a sole subdirectory nested in a collection without every parent directory up to the root collection also getting submitted as a value (until it reaches a directory that contains a second item). One way where the previous behavior could be a problem is if you have a collection: Collection/subdir/reference, but lets say subdir also contains files that you don't want to give to the tool. With cascading selections, selecting reference would auto select subdir and Collection. With cascading disabled you can just select reference. Depending on how various tools handle directory parameters, it might also be desirable to select subdir and not reference if the tool doesn't recurse automatically and you only want it to process files in the parent directory. I think there's more room for improvement though:
  • If you have a large structure of folders and need to select them all, it would be more tedious this way - but it should only be a problem if you have a tool that doesn't recurse
  • We could possibly further refine how selections cascade so that we can enable selecting all collections in a project - for example instead of disabling selection cascading entirely, we could change it so that a selection cascades downwards until it reaches an item type that matches what the picker accepts. So selecting a project with collections will cascade to the root collections without selecting collection contents for both collection and directory pickers, while a file picker would cascade into each collection to select all files. In the end I decided just disabling the cascading behavior for the directory array picker would be best for the scope of the ticket

Merged in arvados-workbench2|adec01514f703975a19b56b2582f6cfb06f1c79f