The departments currently using Google Drive frequently change convention on how to name and structure their folders, inevitably leading to destructive or time-wasting scenarios where departments are out-of-sync.
To hedge against the potential risk of this, extending the GDrive library to validate a directory against a given schema would give a developer a programmatic way to report on these issues.
Proposed option(s)
exclusive boolean (default: false)
By default, validation function should only respond with the files from the schema that are not currently in the directory.
When true, this should also return files that are not in the schema, but are present in the directory. This could potentially flag edge cases that have, so far, evaded a developer's solution.
Abstract
The departments currently using Google Drive frequently change convention on how to name and structure their folders, inevitably leading to destructive or time-wasting scenarios where departments are out-of-sync.
To hedge against the potential risk of this, extending the GDrive library to validate a directory against a given schema would give a developer a programmatic way to report on these issues.
Proposed option(s)
exclusive
boolean(default: false)true, this should also return files that are not in the schema, but are present in the directory. This could potentially flag edge cases that have, so far, evaded a developer's solution.