drive_v3 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 882a97d3563d0c5565e00ae57c230fbef5fcd94b233dfe4281cfbaaa81ed4bbe
+  data.tar.gz: 215a903e2c6f89652ae2da0e8a3ad55ad0294a170982206e9525f1c572fc8ab0
+SHA512:
+  metadata.gz: 42a1dca40e3e0fcd85c679ffd90b906bd0ef0cc3e384b0aa5121999b5122dc174fd0c379bb3d2aafcabca14b5984246dde28a4cf53023e9de79ba423232f9916
+  data.tar.gz: 54a99a6bf6b9751914def5bece84593e1423045867a40e126d8c9bc749a79adcb2288d8f7f42a3d3ed46a90f0dfa96910047e255409a81551a452b4bfefaf005

data/.markdownlint.yml

@@ -0,0 +1,25 @@
+default: true
+
+# Unordered list indentation
+MD007: { indent: 2 }
+
+# Line length
+MD013: { line_length: 90, tables: false, code_blocks: false }
+
+# Heading duplication is allowed for non-sibling headings
+MD024: { siblings_only: true }
+
+# Do not allow the specified trailig punctuation in a header
+MD026: { punctuation: '.,;:' }
+
+# Order list items must have a prefix that increases in numerical order
+MD029: { style: 'ordered' }
+
+# Lists do not need to be surrounded by blank lines
+MD032: false
+
+# Allow raw HTML in Markdown
+MD033: false
+
+# Allow emphasis to be used instead of a heading
+MD036: false

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,37 @@
+AllCops:
+  NewCops: enable
+  # Output extra information for each offense to make it easier to diagnose:
+  DisplayCopNames: true
+  DisplayStyleGuide: true
+  ExtraDetails: true
+  SuggestExtensions: false
+  # RuboCop enforces rules depending on the oldest version of Ruby which
+  # your project supports:
+  TargetRubyVersion: 3.1
+
+Gemspec/DevelopmentDependencies:
+  EnforcedStyle: gemspec
+
+# The default max line length is 80 characters
+Layout/LineLength:
+  Max: 120
+
+# The DSL for RSpec and the gemspec file make it very hard to limit block length:
+Metrics/BlockLength:
+  Exclude:
+    - "spec/spec_helper.rb"
+    - "spec/**/*_spec.rb"
+    - "*.gemspec"
+
+Metrics/ModuleLength:
+  CountAsOne: ['hash']
+
+# When writing minitest tests, it is very hard to limit test class length:
+Metrics/ClassLength:
+  CountAsOne: ['hash']
+  Exclude:
+    - "test/**/*_test.rb"
+
+Style/AsciiComments:
+  Enabled: false
+

data/.yardopts

@@ -0,0 +1,6 @@
+--no-private
+--hide-void-return
+--markup-provider=redcarpet
+--markup markdown
+- CHANGELOG.md
+- LICENSE.txt

data/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Change Log
+
+Changes for each release are listed in this file.
+
+This project adheres to [Semantic Versioning](https://semver.org/) for its releases.
+
+## v0.2.0 (2023-12-04)
+
+[Full Changelog](https://github.com/main-branch/drive_v3/compare/v0.1.0..v0.2.0)
+
+Changes since v0.1.0:
+
+* e23a653 Add parameters to support searching all drives (#4)
+
+## v0.1.0 (2023-12-02)
+
+[Full Changelog](https://github.com/main-branch/drive_v3/compare/cadfd09..v0.1.0)
+
+Changes:
+
+* 75e1077 Fix links in the READMEs (#2)
+* 671e412 Add examples for managing files and permissions (#1)
+* d0bab77 Update examples documentation
+* cadfd09 Initial commit

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at jcouball@yahoo.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2023 James Couball
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,436 @@
+# DriveV3
+
+[![Gem Version](https://badge.fury.io/rb/drive_v3.svg)](https://badge.fury.io/rb/drive_v3)
+[![Documentation](https://img.shields.io/badge/Documentation-Latest-green)](https://rubydoc.info/gems/drive_v3/)
+[![Change Log](https://img.shields.io/badge/CHANGELOG-Latest-green)](https://rubydoc.info/gems/drive_v3/file/CHANGELOG.md)
+[![Build Status](https://github.com/main-branch/drive_v3/workflows/CI%20Build/badge.svg?branch=main)](https://github.com/main-branch/drive_v3/actions?query=workflow%3ACI%20Build)
+[![Maintainability](https://api.codeclimate.com/v1/badges/aeebc016487c5cad881e/maintainability)](https://codeclimate.com/github/main-branch/drive_v3/maintainability)
+[![Test Coverage](https://api.codeclimate.com/v1/badges/aeebc016487c5cad881e/test_coverage)](https://codeclimate.com/github/main-branch/drive_v3/test_coverage)
+
+Unofficial helpers and extensions for the Google Drive V3 API
+
+* [Installation](#installation)
+* [Examples](#examples)
+* [Important links for programming Google Drive](#important-links-for-programming-google-drive)
+  * [DriveV3 documenation](#drivev3-documenation)
+  * [General API documentation](#general-api-documentation)
+  * [Ruby implementation of the Drive API](#ruby-implementation-of-the-drive-api)
+  * [Other links](#other-links)
+* [Getting started](#getting-started)
+  * [Create a Google Cloud project](#create-a-google-cloud-project)
+  * [Enable the APIs you want to use](#enable-the-apis-you-want-to-use)
+  * [Download a Google API credential file](#download-a-google-api-credential-file)
+* [Usage](#usage)
+  * [Obtaining an authenticated DriveService](#obtaining-an-authenticated-driveservice)
+  * [Building a request](#building-a-request)
+    * [Method 1: constructing requests using `Google::Apis::SheetsV4::*` objects](#method-1-constructing-requests-using-googleapissheetsv4-objects)
+    * [Method 2: constructing requests using hashes](#method-2-constructing-requests-using-hashes)
+    * [Which method should be used?](#which-method-should-be-used)
+  * [Validating requests](#validating-requests)
+  * [Google Extensions](#google-extensions)
+    * [SheetsService Extensions](#sheetsservice-extensions)
+    * [Spreadsheet Extensions](#spreadsheet-extensions)
+    * [Sheet Extensions](#sheet-extensions)
+  * [Working with dates and times](#working-with-dates-and-times)
+  * [Working with colors](#working-with-colors)
+* [Development](#development)
+* [Contributing](#contributing)
+* [License](#license)
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+```shell
+bundle add drive_v3
+```
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+```shell
+gem install drive_v3
+```
+
+## Examples
+
+Many examples can be found in the `examples` directory of this project. The examples
+have [a README of their own](https://github.com/main-branch/drive_v3/blob/main/examples/README.md)
+which describes each example.
+
+Prior to running an example, clone this project and run `bundle install` in the
+project's root working directory.
+
+Run an example using `bundle exec`. For example, to run the `set_background_color1`
+example:
+
+```shell
+bundle exec examples/set_background_color1
+```
+
+## Important links for programming Google Drive
+
+### DriveV3 documenation
+
+This Gem's YARD documentation is hosted on [rubydoc.info]https://rubydoc.info/gems/drive_v3/.
+
+### General API documentation
+
+* [Google Drive API Overview](https://developers.google.com/drive/api)
+* [Google Drive API Reference](https://developers.google.com/drive/api/reference/rest)
+* [Discovery Document for the Drive API](https://www.googleapis.com/discovery/v1/apis/drive/v3/rest)
+
+### Ruby implementation of the Drive API
+
+* [DriveService Class](https://github.com/googleapis/google-api-ruby-client/blob/main/generated/google-apis-drive_v3/lib/google/apis/drive_v3/service.rb)
+* [All Other Drive Classes](https://github.cofilem/googleapis/google-api-ruby-client/blob/main/generated/google-apis-drive_v3/lib/google/apis/drive_v3/classes.rb)
+
+### Other links
+
+* None yet!
+
+## Getting started
+
+In order to use this gem, you will need to obtain a Google API service account
+credential following the instructions below.
+
+### Create a Google Cloud project
+
+Create a Google Cloud project using [these directions](https://developers.google.com/workspace/guides/create-project).
+
+### Enable the APIs you want to use
+
+Enable the Drive API for this project using [these directions](https://developers.google.com/workspace/guides/enable-apis).
+
+### Download a Google API credential file
+
+Create a service account and download a credential file using [these directions](https://developers.google.com/workspace/guides/create-credentials#service-account).
+
+You can store the download credential files anywhere on your system.
+The recommended location is `~/.google-api-credential.json` since this is default
+credential file that `DriveV3.drive_service` uses.
+
+## Usage
+
+[Detailed API documenation](https://rubydoc.info/gems/drive_v3/) is hosted on rubygems.org.
+
+### Obtaining an authenticated DriveService
+
+Typically, to construct an authenticated DriveService object where the credential
+is read from a file, the following code is required:
+
+```Ruby
+require 'googleauth'
+drive_service = Google::Apis::DriveV3::DriveService.new
+credential = File.read(File.expand_path('~/google-api-credential.json')) do |credential_source|
+  scopes = Google::Apis::DriveV4::AUTH_DRIVE
+  options = { json_key_io: credential_source, scope: scopes }
+  Google::Auth::DefaultCredentials.make_creds(options).tap(&:fetch_access_token)
+end
+drive_service.authorization = credential
+```
+
+The `SheetsV4.sheets_service` method simplifies this a bit.
+
+By default, the credential is read from `~/.google-api-credential.json`. In that case,
+an authenticated SheetsService object can be obtained with one method call:
+
+```Ruby
+sheets_service = SheetsV4.sheets_service
+```
+
+If the credential is stored somewhere else, pass the `credential_source` to
+`SheetsV4.sheets_service` manually. `credential_source` can be a String:
+
+```Ruby
+sheets_service = SheetsV4.sheets_service(credential_source: File.read('credential.json'))
+```
+
+an IO object:
+
+```Ruby
+sheets_service = File.open('credential.json') do |credential_source|
+  SheetsV4.sheets_service(credential_source:)
+end
+```
+
+or an already constructed `Google::Auth::*` object.
+
+### Building a request
+
+To use the Sheets API, you need to construct JSON formatted requests.
+
+These requests can be constructed using two different methods:
+1. constructing requests using `Google::Apis::SheetsV4::*` objects or
+2. constructing requests using hashes
+
+The following two sections show how each method can be used to construct
+a request to update a row of values in a sheet.
+
+For these two examples, values in the `values` array will be written to the
+sheet whose ID is 0. The values will be written one per row starting at cell A1.
+
+```Ruby
+values = %w[one two three four] # 'one' goes in A1, 'two' goes in A2, etc.
+```
+
+The method `SheetsService#batch_update_spreadsheet` will be used to write the values. This
+method takes a `batch_update_spreadsheet_request` object with a `update_cells` request
+that defines the update to perform.
+
+#### Method 1: constructing requests using `Google::Apis::SheetsV4::*` objects
+
+When using this method, keep the Ruby source file containing the SheetsService class
+([google/apis/drive_v3/service.rb](https://github.com/googleapis/google-api-ruby-client/blob/main/generated/google-apis-drive_v3/lib/google/apis/drive_v3/service.rb))
+and the Ruby source file containing the defitions of the request & data classes
+([lib/google/apis/drive_v3/classes.rb](https://github.com/googleapis/google-api-ruby-client/blob/main/generated/google-apis-drive_v3/lib/google/apis/drive_v3/classes.rb))
+open for easy searching. These files will give you all the information you need
+to construct valid requests.
+
+Here is the example constructing requests using `Google::Apis::SheetsV4::*` objects
+
+```Ruby
+def values = %w[one two three four]
+
+def row_data(value)
+  Google::Apis::SheetsV4::RowData.new(
+    values: [
+      Google::Apis::SheetsV4::CellData.new(
+        user_entered_value:
+          Google::Apis::SheetsV4::ExtendedValue.new(string_value: value.to_s)
+      )
+    ]
+  )
+end
+
+def rows
+  values.map { |value| row_data(value) }
+end
+
+def write_values_request
+  fields = 'user_entered_value'
+  start = Google::Apis::SheetsV4::GridCoordinate.new(
+    sheet_id: 0, row_index: 0, column_index: 0
+  )
+  Google::Apis::SheetsV4::Request.new(
+    update_cells: Google::Apis::SheetsV4::UpdateCellsRequest.new(rows:, fields:, start:)
+  )
+end
+
+requests = Google::Apis::SheetsV4::BatchUpdateSpreadsheetRequest.new(requests: [write_values_request])
+
+spreadsheet_id = '18FAcgotK7nDfLTOTQuGCIjKwxkJMAguhn1OVzpFFgWY'
+SheetsV4.sheets_service.batch_update_spreadsheet(spreadsheet_id, requests)
+```
+
+#### Method 2: constructing requests using hashes
+
+When constructing requests using this method, keep the [Google Sheets Rest API Reference](https://developers.google.com/sheets/api/reference/rest)
+documentation open. In particular, [the Batch Update Requests page](https://developers.google.com/sheets/api/reference/rest/v4/spreadsheets/request#cutpasterequest)
+is particularly useful for building spreadsheet batch update requests.
+
+One caveat to keep in mind is that the Rest API documents object properties using
+Camel case BUT the Ruby API requires snake case.
+
+For instance, the Rest API documents the properties for a grid coordinate to be
+"sheetId", "rowIndex", and "columnIndex". However, in the Ruby API, you should
+construct this object using snake case:
+
+```Ruby
+grid_coordinate = { sheet_id: 0, row_index: 0, column_index: 0 }
+```
+
+Here is the example constructing requests using hashes:
+
+```Ruby
+def values = %w[one two three four]
+
+def rows
+  values.map do |value|
+    { values: [{ user_entered_value: { string_value: value } }] }
+  end
+end
+
+def write_values_request
+  fields = 'user_entered_value'
+  start = { sheet_id: 0, row_index: 0, column_index: 0 }
+  { update_cells: { rows:, fields:, start: } }
+end
+
+requests = { requests: [write_values_request] }
+
+spreadsheet_id = '18FAcgotK7nDfLTOTQuGCIjKwxkJMAguhn1OVzpFFgWY'
+response = SheetsV4.sheets_service.batch_update_spreadsheet(spreadsheet_id, requests)
+```
+
+#### Which method should be used?
+
+Either method will do the same job. I prefer "Method 2: constructing requests using
+hashes" because my code is more concise and easy to read.
+
+While either method can produce a malformed request, "Method 2" is more likely to
+result in malformed requests. Unfortunately, when given a malformed request, the
+Google Sheets API will do one of following depending on the nature of the problem:
+
+1. Raise a `Google::Apis::ClientError` with some additional information
+2. Raise a `Google::Apis::ClientError` with no additional information (this the most
+   common result)
+3. Not return an error with some of the batch requests not having the expected outcome
+
+Luckily, this library provides a way to validate that requests are valid and
+identifies precisely where the request objects do not conform to the API description.
+That is the subject of the next section [Validating requests](#validating-requests).
+
+### Validating requests
+
+The [`SheetsV4.validate_api_object`](https://rubydoc.info/gems/drive_v3/SheetsV4#validate_api_object-class_method)
+method can be used to validate request objects prior to using them in the Google
+Sheets API.
+
+This method takes a `schema_name` and an `object` to validate. Schema names can be
+listed using [`SheetsV4.api_object_schema_names`](https://rubydoc.info/gems/drive_v3/SheetsV4#api_object_schema_names-class_method).
+
+This method will either return `true` if `object` conforms to the schema OR it
+will raise a RuntimeError noting where the object structure did not conform to
+the schema.
+
+In the previous examples (see [Building a request](#building-a-request)), the
+following line can be inserted after the `requests =  ...` line to validate the
+request:
+
+```Ruby
+SheetsV4.validate_api_object(schema: 'batch_update_spreadsheet_request', object: requests)
+```
+
+### Google Extensions
+
+The `SheetsV4::GoogleExtensions` module provides extensions to the `Google::Apis::SheetsV4`
+classes to simplify use of the SheetsV4 API.
+
+These extensions are not loaded by default and are not required to use other parts
+of this Gem. To enable these extension, you must:
+
+```Ruby
+require 'drive_v3/google_extensions'
+```
+
+#### SheetsService Extensions
+
+Functionality is added to `get_spreadsheet` to set the `sheets_service` attribute on
+the returned spreadsheet and set the `sheets_service` and `spreadsheet` attributes
+on the sheets contained in the spreadsheet.
+
+This can simplify complex spreadsheet updates because you won't have to pass a
+sheets_service, spreadsheet, and sheet objects separately.
+
+#### Spreadsheet Extensions
+
+The `sheets_service` attribute is added and is set by `SheetsService#get_spreadsheet`.
+
+Convenience methods for getting sheets within the spreadsheet are added:
+
+* `sheet(id_or_title)`: returns the sheet matching the id or title given
+* `sheet_id(title)`: returns the ID  for the sheet matching the title given
+* `each_sheet(ids_or_titles)`: enumerates the sheets within a spreadsheet matching
+  the given IDs or titles.
+
+#### Sheet Extensions
+
+The `sheets_service` and `spreadsheet` attributes are added. Both are set when the
+sheet's spreadsheet is loaded by `SheetsService#get_spreadsheet`.
+
+### Working with dates and times
+
+Google Sheets, similar to other spreadsheet programs, stores dates and date-time
+values as numbers. This system makes it easier to perform calculations with
+dates and times.
+
+This gem provides two sets of equavalent conversion methods. The first set is defined
+as class methods on the `SheetsV4` class.
+
+* `SheetsV4.date_to_gs(date)` returns a numeric cell value
+* `SheetsV4.gs_to_date(cell_value)` returns a Date object
+* `SheetsV4.datetime_to_gs(datetime)` returns a numeric cell value
+* `SheetsV4.gs_to_datetime(cell_value)` returns a DateTime object
+
+In order to convert to and from spreadsheet values, the spreadsheet timezone must
+be known. A spreadsheet's timezone is found in the Google Sheets spreadsheet object's
+properties:
+
+```Ruby
+SheetsV4.default_spreadsheet_tz = spreadsheet.properties.time_zone
+```
+
+If a time zone is not set using `SheetsV4.default_spreadsheet_tz`, a RuntimeError
+will be raised when any of the above methods are used.
+
+Here is an example of how the timezone can change the values fetched from the
+spreadsheet:
+
+```Ruby
+cell_value = 44333.191666666666
+
+SheetsV4.default_spreadsheet_tz = 'America/New_York'
+datetime = SheetsV4.gs_to_datetime(cell_value) #=> Mon, 17 May 2021 04:36:00 -0400
+datetime.utc #=> 2021-05-17 08:36:00 UTC
+
+SheetsV4.default_spreadsheet_tz = 'America/Los_Angeles'
+datetime = SheetsV4.gs_to_datetime(cell_value) #=> Mon, 17 May 2021 04:36:00 -0700
+datetime.utc #=> 2021-05-17 11:36:00 UTC
+```
+
+Valid time zone names are those listed in one of these two sources:
+
+* `ActiveSupport::TimeZone.all.map { |tz| tz.tzinfo.name }`
+* `ActiveSupport::TimeZone.all.map(&:name)`
+
+The `SheetsV4` methods works well if the spreadsheet timezone is constant through
+the run of the program. If this is not the case -- for instance when working with
+multiple spreadsheets whose timezones may be different -- then use
+`SheetsV4::ConvertDatesAndTimes`.
+
+Each instance of `SheetsV4::ConvertDatesAndTimes` has it's own spreadsheet timezone
+used in the conversions. Instance methods for this class are the same as the
+date conversion methods on the SheetsV4 class.
+
+Example:
+
+```Ruby
+cell_value = 44333.191666666666
+converter = SheetsV4::ConvertDatesAndTimes.new('America/Los_Angeles')
+datetime = SheetsV4.gs_to_datetime(cell_value) #=> Mon, 17 May 2021 04:36:00 -0700
+datetime.utc #=> 2021-05-17 11:36:00 UTC
+```
+
+### Working with colors
+
+Color objects (with appropriate :red, :green, :blue values) can be retrieved by name
+using `SheetsV4.color(:black)` or `SheetsV4::Color.black` (these are equivalent).
+
+Color names can be listed using `SheetsV4.color_names`.
+
+The color object returned is a Hash as follows:
+
+```Ruby
+SheetsV4::Color.black #=> {:red=>0.0, :green=>0.0, :blue=>0.0}
+```
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies and then, run
+`rake` to run the tests, static analysis, etc. You can also run `bin/console` for an interactive
+prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To
+release a new version, update the version number in `version.rb`, and then run
+`bundle exec rake release`, which will create a git tag for the version, push git
+commits and the created tag, and push the `.gem` file to
+[rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on [the main-branch/drive_v3 GitHub project](https://github.com/main-branch/drive_v3).
+
+## License
+
+The gem is available as open source under the terms of the
+[MIT License](https://opensource.org/licenses/MIT).