A chrome.storage.* adapter for Backbone.js, largely inspired by Backbone.localStorage but reworked for use in writing extensions for the Chrome browser.
The asynchronous nature of Chrome's storage API is handled with $.Deferred objects wrapped around its methods, which allows for essentially the same flexibility that is provided by AJAX requests, e.g.:
collection.fetch().then(
// done callback
function() {
console.log('do something once collection is fetched');
},
// fail callback
function(dfd, errText, lastError /* from chrome.runtime.lastError */) {
console.warn("Problem fetching from chromeStorage '%s'", errText);
}
);
Backbone.ChromeStorage supports AMD/RequireJS, but it will work without it.
Usage is much the same as with localStorage, with the addition of an extra (optional) argument that specifies which type of storage to use:
var SomeCollection = Backbone.Collection.extend({
chromeStorage: new Backbone.ChromeStorage("SomeCollection", "sync");
// everything else is the same
});
For storage that will persist across every browser a user has synchronized, use "sync". For storage that will persist only in the current browser, much like localStorage, use "local".
If a type is not provided, it will default to "local". To change the default, use Backbone.ChromeStorage.defaultType.
If a user has disabled Chrome's synchronization features, "sync" will automatically fall back to "local" without issue.
You must remember to request the storage permission in your manifest.json file.
{
"name": "My extension",
...
"permissions": [
"storage"
],
...
}
See the chrome.storage reference guide for more details.
Backbone.ChromeStorage will work just fine with Zepto instead of jQuery, but as it requires deferred objects, you will need to use something like the excellent simply-deferred.
Because they both modify globals, Backbone.ChromeStorage and Backbone.localStorage will not play nice together. Using the 'local' type for ChromeStorage is effectively the same as localStorage if you wish to mix the two.
Chrome's rate-limiting and quota restrictions on "sync" storage are presently handled by $.Deferred().reject(), with chrome.runtime.lastError being passed to any fail callbacks as the third argument. A future version will handle this more elegantly.
- 2013 / 06 / 03
- Don't stringify objects when persisting (Issue #5)
- @nigggle
Released under MIT license
Copyright (c) 2012-2013 Alexandra Grey
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.