Arvados

I have been studying which would be the best way to avoid getting the manifest_text field from the collection's GET requests.

We already support the select param to pass an array of field names to be included on the request. The problem I'm seeing is that passing a hardcoded array of strings isn't future-proof because we could be adding new fields to the collection model that would require updating the code on wb2.

I've been trying to find a dynamic way of doing this on TypeScript, but I think there's no good way currently, as interfaces & types exist only in TS, so no type-reflection can be made once the app is compiled for production.

The only two options I'm seeing (besides adding a exclude param to the backend) are:

• Hard-code the field names array
• Use the discovery document to build the array on the app's bootup procedure.

I'm not sure if there're significant downsides to the 2nd option, but it would be my preferred choice.

From chat: Peter suggested using a "list" request with filters so that manifest_text fields won't be received.

Updates at arvados-workbench2|34e3489e - branch 18484-collection-manifest-fix
Test run: developer-tests-workbench2: #521

• Makes CollectionService.get() to use the list request under the hood, with a uuid filter.
• Adds test.

Updates at arvados-workbench2|30ef6aaa
Test run: developer-tests-workbench2: #522

• Adds "include_old_versions: true" param & select support to CollectionService.get()
• Fixes related code so that the manifest_text field is requested where needed.
• Adds test.

Lgtm