Usage with Quasar v2 and BEX (Browser Extension) Mode #18
Replies: 2 comments 3 replies
-
Update: The example should work 🤔. Could you provide more examples of your Sorry, I misunderstood the API 🥲, your example is right, the get: (keys?: string | string[] | object, callback?: function) => {...} But the callback function will be passed an object 🤔 : chrome.storage.sync.get(key, (value) => {
- resolve(value)
+ resolve(value[key])
}); ... Object with items in their key-value mappings. Original:
- chrome.storage.sync.get(key, (value) => {
+ chrome.storage.sync.get([key], (value) => {
resolve(value)
}); |
Beta Was this translation helpful? Give feedback.
-
@iendeavor Thanks for your reply. I've edited my
I'm using the Quasar v2 framework, so I guess the setup might be non-standard. I have a store at
When I run the |
Beta Was this translation helpful? Give feedback.
-
Hi,
Wondering if anyone has successfully gotten this working with Quasar in BEX mode?
Here's my
stores/index.ts
file:For example, I see 'pinia' in the log, but when I make any changes to the state in my actions, none of the storage functions run and nothing ends up in my Chrome storage?
Beta Was this translation helpful? Give feedback.
All reactions