Drive.revisions.list未返回lastModifyingUserName或lastModifyingUser [英] Drive.revisions.list isn't returning lastModifyingUserName or lastModifyingUser

问题描述

https：//开发人员。 google.com/apis-explorer/#p/drive/v2/drive.revisions.list?fileId= &安培;字段=项（ID％252ClastModifyingUser％252ClastModifyingUserName％252Cmd5Checksum％252CmodifiedDate）及_h = 5&安培;

我们有一个基于文档列表的应用程序，它使用旧版本API列出谁修改了文件的用户名。 Drive API和drive.revisions.list似乎没有返回用户名，所以我们将无法使用它来显示谁更改了旧版本。

缺少我们的用户名是我们的阻挡者之一迁移到新的API。

其他字段，例如md5sum也缺失。

解决方案

同样的结果转载。现在报告此问题。

现在，您可以使用Files.get（），它将返回lastModifyingUser对整个文件的最新更改，尽管您无法查看lastModifyingUser每个版本。

https://developers.google.com/apis-explorer/#p/drive/v2/drive.revisions.list?fileId=&fields=items(id%252ClastModifyingUser%252ClastModifyingUserName%252Cmd5Checksum%252CmodifiedDate)&_h=5&

We have an a documents list based app which uses the old revisions API to list usernames of who modified a file. It seems with the Drive API and drive.revisions.list, there is no username being returned, so we won't be able to use it to show who changed an older revision.

The lack of our user names is one of our blockers to migrate over to the new API.

Other fields such as the md5sum as missing as well.

解决方案

Same result reproduced. This issue is reported now.

For now, you can use Files.get() which will return lastModifyingUser of latest change of the whole file, although you cannot view lastModifyingUser for each revision.

这篇关于Drive.revisions.list未返回lastModifyingUserName或lastModifyingUser的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！