Add missing fields in Drive V2 API parser.

Add missing fields in Drive V2 API parser.

These added fields are necessary to work with our file system
implementation.

BUG=chromium:127728
TEST=unit_tests --gtest_filter="DriveAPI*"

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=150291

[kochi, 2012-08-07 04:05:30]

Ryo,

Could you review this CL?
Thanks,

[hashimoto, 2012-08-07 04:19:02]

https://chromiumcodereview.appspot.com/10855017/diff/1/chrome/browser/chromeo...
File chrome/browser/chromeos/gdata/drive_api_parser.cc (right):

https://chromiumcodereview.appspot.com/10855017/diff/1/chrome/browser/chromeo...
chrome/browser/chromeos/gdata/drive_api_parser.cc:88: const char
kAlternateLink[] = "alternateLink";
Is there a policy to order these values?
If so, please add a comment.
If not, please order them in a reasonable manner.

https://chromiumcodereview.appspot.com/10855017/diff/1/chrome/browser/chromeo...
chrome/browser/chromeos/gdata/drive_api_parser.cc:92: const char
kExplicitlyTrashed[] = "explicitlyTrashed";
What is this for?

[kochi, 2012-08-07 05:24:37]

Thanks for your quick review!

https://chromiumcodereview.appspot.com/10855017/diff/1/chrome/browser/chromeo...
File chrome/browser/chromeos/gdata/drive_api_parser.cc (right):

https://chromiumcodereview.appspot.com/10855017/diff/1/chrome/browser/chromeo...
chrome/browser/chromeos/gdata/drive_api_parser.cc:88: const char
kAlternateLink[] = "alternateLink";
Basically this order follows the order in Drive V2 API
web document.

Added a comment about the order and links for each structure.

https://chromiumcodereview.appspot.com/10855017/diff/1/chrome/browser/chromeo...
chrome/browser/chromeos/gdata/drive_api_parser.cc:92: const char
kExplicitlyTrashed[] = "explicitlyTrashed";
Removed.

[hashimoto, 2012-08-07 05:55:04]

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
File chrome/browser/chromeos/gdata/drive_api_parser.cc (right):

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
chrome/browser/chromeos/gdata/drive_api_parser.cc:382:
converter->RegisterCustomField<base::Time>(
Could you order these too?

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
File chrome/browser/chromeos/gdata/drive_api_parser.h (right):

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
chrome/browser/chromeos/gdata/drive_api_parser.h:331: const base::Time&
created_date() const { return created_date_; }
Could you order these values too?

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
chrome/browser/chromeos/gdata/drive_api_parser.h:383: base::Time created_date_;
ditto.

[kochi, 2012-08-07 06:30:37]

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
File chrome/browser/chromeos/gdata/drive_api_parser.cc (right):

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
chrome/browser/chromeos/gdata/drive_api_parser.cc:382:
converter->RegisterCustomField<base::Time>(
On 2012/08/07 05:55:04, hashimoto wrote:
> Could you order these too?

Done.

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
File chrome/browser/chromeos/gdata/drive_api_parser.h (right):

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
chrome/browser/chromeos/gdata/drive_api_parser.h:331: const base::Time&
created_date() const { return created_date_; }
On 2012/08/07 05:55:04, hashimoto wrote:
> Could you order these values too?

Done.

https://chromiumcodereview.appspot.com/10855017/diff/8001/chrome/browser/chro...
chrome/browser/chromeos/gdata/drive_api_parser.h:383: base::Time created_date_;
On 2012/08/07 05:55:04, hashimoto wrote:
> ditto.

Done.

[hashimoto, 2012-08-07 06:38:58]

lgtm