Various bug fixes and enhancements

[rafaelgomesxyz]

This will be another big PR (hopefully the last one before the release). I hope to go over everything left on my to-do list.

[rafaelgomesxyz]

@MrMamen Google offers a free tier with their cloud products, so I think it's better to store the database there instead of the Google Sheet. I separated a subdomain in my domain and was making some tests, and it seems to work quite well. Example: https://uts.rafaelgomes.xyz/api/correction-suggestions?ids=netflix_80103820,netflix_80103821 If it takes a while to load, it's because the instance was suspended (Google suspends instances that are idle for too long to save resources).

The free tier offers 28 instance hours per day (since we'll only use one instance, we'll only need 24 hours at most), and 50.000 database writes / 20.000 database reads per day (which I think should be more than enough).

If that's ok with you, I'll add uts.rafaelgomes.xyz as a required permission and make the appropriate changes.

[MrMamen]

Sure go ahead. It might be slightly harder to check the list, but it will probably be a smoother experience for the users.

[rafaelgomesxyz]

For us, not really. I added you to the project, so if you go to https://console.cloud.google.com/firestore/data/?project=trakt-tools-uts you should be able to see the database.

[rafaelgomesxyz]

Will start pushing commits tomorrow, since there are a lot of changes, in case you want to start reviewing them.

I think we can finally release it this month. This PR will fix #44, #46 and #72, and the only other issue that would be nice to fix before release is #47, but I think I can do that one quickly after I'm done with this PR. Will see how much I can do this weekend.

[rafaelgomesxyz]

Had to deal with something last week, so didn't have time to work on it, but now I do.

I decided to make separate PRs in the end, to separate things better. First one is up: #81

[rafaelgomesxyz]

@MrMamen I'm currently working on a PR to replace history pages with infinite scrolling. Just wondering if you're ok with that or if you think we should keep the pages.

I think the infinite scrolling is better because we don't have to worry about each page, and it also makes it easier to load more items if some items have been filtered. Right now, even if itemsToLoad is set to 10 and, let's say, 5 items were filtered because they're already synced, the page will display only 5 items. With infinite scrolling, we can load items on demand, so it doesn't matter how many items were filtered, it will always load more.

In that PR, I'm also removing the itemsToLoad option and making it always load 10, because since it's infinite scrolling, it doesn't make sense to allow the user to specify how much to load each time, and I think 10 is a good number. Let me know if you think we should keep this option as well.

[MrMamen]

@rafaelgomesxyz I think infinite scrolling is great.

[rafaelgomesxyz]

I think we can finally release it this month.

And two months passed... lol

I'll try to finish the last PRs this next week. Only things I have left to do:

• final dependency update, to get rid of some deprecated or outdated packages (Material-UI v4 to v5, moment to date-fns, etc.)
• better typings (generic request response, split Item into Episode and Movie, remove all never types, etc.)
• better errors (make sure that every error is properly dealt with)
• fix any known remaining bugs (this PR)
• prepare for traktflix migration
• release

[MrMamen]

Any progress on this one?

[rafaelgomesxyz]

Still working on it, but been a bit busy recently. Almost done with the better typings PR.