scarygami/chrome-storage

Get/store values via the Chrome Storage API

chrome-storage

Get/store values via the Chrome Storage API.

This repository is also meant as an example how to develop Polymer elements for Chrome Apps, with testing work flows. (related article)

Dependencies

With Node.js installed, run the following one liner from the root of this project to install all dependencies:

npm install -g gulp bower && npm install && bower install

Development workflows

Test

gulp build:test

This will build a Chrome App based on the tests in the test folder into test-app which can be loaded as "Unpacked Extension" in Chrome to run the tests with the Chrome Apps APIs available.

gulp live:test

This will build the same Chrome App but with live reloading enabled.

Demo

gulp build:demo

This will build a Chrome App based on the demo folder into demo-app which can be loaded as "Unpacked Extension" in Chrome to show your element in acation

gulp live:demo

This will build the same Chrome App but with live reloading enabled.

chrome-storage's Issues

An `auto` attribute instead of `autoSaveDisabled`

Hi,

The Polymer way would be adding an auto attribute instead of opposite functionality like autoSaveDisabled. It's more natural I guess that the element don't do nothing by default (only on request) but it have ability to automatically perform some logic.

It's just a suggestion.
Good work anyway especially with testing.