Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Data Structure
See original GitHub issueHey I’m looking at how the data is stored in TabWrangler and it looks like you’re saving the complete tab data from what the chrome.tabs API gives you.
My question is why not just save the data that is necessary?
Looking at the data, it seems you only need the following:
- title
- url
- pinned
I can’t seem to understand why you need to store the rest of the data, like height, width windows ID etc. Isn’t the rest of the data useless? Why not save users storage data, by reducing the data per tab?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We should include
mutedInfoandincognitoI don’t believe there is any action to take here right now. Tab Wrangler is not wasting much space currently; it’s only text, which compresses easily.
I am going to close this, but please reopen if the size of TW’s storage is causing functionality issues.