docs: Improve documentation around options, especially metadata

Had the read the code to easily see what values I could pass into options like below. Shouldn't have to read the code.

var options = {
  data: data, // png image data
  metadata: {
    contentType: 'image/png'
  }
};

bucket.write('image.png', options, callback);

The docs could definitely use help. JSDoc is our "source of doc truth", so PRs welcome to better annotate parameters, describe functionality, etc.

a47cc9b

Feel free to add more if you think it can be improved.

chore: release 1.1.1 (#161)

fix: do not import the whole google-gax from proto JS (#1553) (#161)

chore: update eslintignore config (#161)

fix(deps): update dependency @google-cloud/common to ^0.28.0 (#161)

fix: drop support for nodejs 9.x (#161)

Update @google-cloud/common to the latest version 🚀 (#161)

fix: drop support for node.js 4.x and 9.x (#161)

Release v0.19.0 (#161)

chore: update lint ignore files (#161)

docs: update jsdoc license/samples-README (#161)

chore: 0.19.2 release proposal (#161)

chore: workaround for repo-tools EPERM (googleapis#161)

Allow raw table mutations. (#161)

Add list_datasets_and_projects sample (#161)

chore(deps): update dependency sinon to v6 (#161)

Allow raw table mutations. (#161)

Allow raw table mutations. (googleapis#161)

Navigation Menu

Repository navigation

docs: Improve documentation around options, especially metadata #161

55 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

docs: Improve documentation around options, especially metadata #161

Description

Activity

stephenplusplus commented on Sep 1, 2014

stephenplusplus commented on Sep 19, 2014

55 remaining items

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions