feat(services/gdrive): Add read & write & delete support for GoogleDrive

[Young-Flash]

#654

[Young-Flash]

What do you think is the appropriate place to store the cache of path to id mapping? @Xuanwo

[Xuanwo]

What do you think is the appropriate place to store the cache of path to id mapping? @Xuanwo

A hashmap in core is good enough.

[Young-Flash]

A hashmap in core is good enough.

I mean who own the hashmap. An intuitive idea is to make it a member of GoogleDriveBackend, but modifying this hashmap in get_file_id_by_path() requires &mut self, while there is &self in gdrive_get(), read()

[Xuanwo]

I mean who own the hashmap.

An Arc<Mutex<HashMap>> in GoogleDriveCore, and GoogleDriveBackend will hold a core: Arc<GoogleDriveCore>

[Young-Flash]

I'd like to left HashMap and other op in next PR to avoid this PR too large. Is there any other problem?

[Xuanwo]

BTW, this branch seems contained not related commits.

[Young-Flash]

BTW, this branch seems contained not related commits.

It's wired, it occurs after I resolved the conflicts.

[Xuanwo]

It's wired, it occurs after I resolved the conflicts.

You can try git reset origin/main and do a force push.

[Xuanwo]

Thanks a lot!