Jostein Kjønigsen
Jostein Kjønigsen
Not that I know of. Sorry. PRs welcome 😄
Ive given the PR a test-run on a few different accounts: * Regular gmail.com account * OG, grandfathered "Google Apps" account * Paid, company GSuite account Results below. ## Regular...
I see storage_info() is implemented using a regexp on text values. Below are the texts Ive seen for my accounts: * Using 0.66 GB * 6.57 GB of 17 GB...
What might help make things easier for you is to separate data-fetching from data-processing into 2 different functions. That way you can unit-test the processing and just add my real...
Nice catch! I was considering merging https://github.com/KartikTalwar/gmail.js/pull/767 today, but do you want to update the PR to also include fixes for that before I merge? 😄
OK. Let's make it so!
I've tried to reproduce on my machine, but it seems to work for me. Without reproducing, it's hard to tell what's wrong. Using the boilerplate repo, what does `Object.keys(gmail.cache.threadCache).length` say...
I'm not sure I fully understand the scope of this bug. From a API usage point of view, are there use-cases which does not work as expected?
In that case, I guess "error" is more severe than it needs to be. But it could be because of something unexpected happening too. How about warning instead of error?
Feel free to give it a try. PRs welcome 🙂