Bug #18834: [Workbench2] uploading a file into a subdirectory of a collection does not work, file always goes into the root of the collection - Arvados Workbench 2 - Arvados

At file collection-service.ts:
- Methods uploadFiles()/uploadFile(): Instead of having a targetLocation param that completely overrides both collectionUuid and file.name for the final fileURL construction, I think it would be more dev-friendly to add a param called something like destPath with '/' as a default value, so that it's used as another component of the fileURL building code. What do you think? Callers that don't specify it will get their uploads to go to the collection's root dir, and others will be able to specify where exactly files should be uploaded, making the code more readable.
Could you add some unit testing on uploadFiles()/uploadFile()? We should be trying to improve the testing coverage whenever we can.
What's the fix at arvados-workbench2|44d370d about? Seems unrelated to this branch.
The new cypress test code doesn't seem to confirm that the file was really uploaded to the correct "subdir/", it just confirms that it was uploaded. Could you add an assertion on that too? One easy way to do it is to re-request the collection's record and check its manifest data.

Actions

New version: https://dev.arvados.org/projects/arvados/repository/arvados-workbench2/revisions/14b107de3fe4c29f4a37f1958bad99e2b82d2b24
Test run: developer-tests-workbench2: developer-tests-workbench2: #644
Branch: 18834-uploading-a-file-into-a-subdirectory-of-a-collection-does-not-work

Added unit tests, made cypress test more strict

Actions

Just one observation:

One of the new unit tests reveals that the code is issuing an upload request with double-slashes (file src/services/collection-service/collection-service.test.ts:L125). Could you fix the code (and update the test assertion) so that it doesn't do that?

Other than that, LGTM.

Actions

#10