The 'downloadTableFile' function seems to have changed return type (from a dict with a key 'path' to a string) and documentation is incorrect. The change resulted from issue SYNPY-403.
This was not listed as a change in the release notes for that issue "Use single endpoint for all downloads". We should improve our release procedure to identify a list of functions that have changed to help automate what we should write in the release notes?
This was documented in the release notes under the removal of cachedir and files return values for downloads. We should have listed all affected functions however.
Agreed - it's difficult to enumerate all of the potential effects. Is it just the docstring that is out of date?
Couldn't changing the return type of a function in the main client be considered a breaking change?
I'm guessing you mean this line in the release:
"Two member variables of the File object, file_entity.cacheDir and file_entity.files is [sic] being DEPRECATED in favor of file_entity.path for finding the location of a downloaded File."
That doesn't indicate to me that I should expect a return type to change, or that I would even be aware the 'downloadTableFile' is somehow affected by changes to the representation of a File entity.
per, Larsson, this function should be deprecated
Fixed, will close corresponding issue on Github and let the issue creator know to reopen if there is still any problem.