Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the storage backend configurable #337

Open
2 tasks
fsmanuel opened this issue Oct 31, 2021 · 0 comments
Open
2 tasks

Make the storage backend configurable #337

fsmanuel opened this issue Oct 31, 2021 · 0 comments
Labels
enhancement

Comments

@fsmanuel
Copy link
Member

fsmanuel commented Oct 31, 2021 •
edited
Loading

The discussion about suporting more storage backends has been sitting there for a while now #153, #255

The main blocker is that it requires an async api to the storage as both localForage and chrome.storage.local have an async api.

To not have breaking changes we would need to support both sync and async apis and a clear path to let the users migrate to the async api.

  • Implement async version
  • Document usage of sync and async api

Join the discussion: #338

Refs:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fsmanuel