Nick Craig-Wood 2f5a2d3c48 drive: Don't return nil Object with nil error from newObject* functions. ... Before this change the newObject* functions could return object=nil with err=nil. The result of these functions are passed outside of the backend code (eg in Copy, Move) and returning a nil object with a nil error leads to crashes elsewhere as it breaks expectations. After this change we return (nil, fs.ErrorObjectNotFound) in these cases. The one place this is actually needd internally (when turning items into listings) we detect that error and use it to mean skip the directory item. This problem was noticed while testing the shortcuts code. It shouldn't happen normally but it is conceivable it could.		2020-04-30 17:11:36 +01:00
..
test	drive: add --drive-import-formats	2018-09-25 15:20:23 +01:00
drive_internal_test.go	build: fix up package paths after repo move	2019-07-28 18:47:38 +01:00
drive_test.go	build: fix up package paths after repo move	2019-07-28 18:47:38 +01:00
drive.go	drive: Don't return nil Object with nil error from newObject* functions.	2020-04-30 17:11:36 +01:00
upload.go	drive: use multipart resumable uploads for streaming and uploads in mount	2020-01-17 22:03:10 +00:00