Skip to content

Conversation

@moos
Copy link
Owner

@moos moos commented Feb 2, 2019

No description provided.

EirikBirkeland and others added 30 commits July 17, 2017 18:45
The browser version assumes that chrome.storage.local uses an API which is compatible with localStorage; which is not the case. Even though I am using chrome.storage.local for my Chrome extension, I would much prefer to keep debug's variable in localStorage, as I consider chrome.storage.local the 'private space' of my extension.

This change obviates the need to support multiple storage types. But if storage type is important, how about supporting a custom storage facility, including chrome.storage.sync? I.e. the user would provide an object that follows the conventions. Just a thought - I certainly don't see the need at this point though.
Drop usage of `chrome.storage` (or make the storage backend pluggable)
…pt (#577)

* Improve usability of Windows notes w/ examples for prompts & npm script

* Made changes requested for pull request

#577 (review)
* Adding TVMLKit support

* removed the check for window/navigationDocument, instead relying on localStorage in the global context on all 'browser' based platforms
* instance extends feature

* add .extend documentation

* allow empty delimiter in extend
feat: Add unit tests for disable return value

fix: Correct spelling in test case description

feat: Test that disable-string works with enable again

Closes #523

docs: Add section about disable return value
Added script in package.json for running Test-suite

Signed-off-by: ossdev07 <[email protected]>
@moos moos merged commit fb16b70 into moos:master Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.