Describe the bug
I've been adding repositories to the filters over time when I receive a new repository to work with and since my filters are frequently being increased, I probably notice this bug more frequently than others.
For instance, today, when I first loaded the page, it had all the 94 repositories in the filter. But then I reloaded the page and it went down to 87, which is a couple months old filter. Since I'm getting this bug quite frequently, I learned to copy the json from the Session Storage and keep it in a file to fix the issue immediately, but it's still annoying and I may not notice when the filters go down.
Since I fixed this version of the filters with the saved json, next time this bug happens, it will show me 94 when I actually have more than that.
My hypothesis is that you are saving this json in multiple places and only one is being saved at any given time when we hit save. Then, for some reason, the main save doesn't show up in the Session Storage and you show like a backup copy from an older save.
I should probably try to test my hypothesis before opening this issue, but if I'm wrong, you would know, so you could find a way to fix it anyway
To Reproduce
Steps to reproduce the behavior:
F5 or just reopen the page from the sidenav
Filters sometimes revert to an older version
If you let it alone for a while and then reload again, the filters get back to normal
Expected behavior
Keep filters
Desktop (please complete the following information):
OS: Windows
Browser: Yandex Browser, which is a Chromium browser, but I've asked coworkers who use Chrome and they also reported the issue. The workaround I'm using was a suggestion from a Chrome user.
Describe the bug I've been adding repositories to the filters over time when I receive a new repository to work with and since my filters are frequently being increased, I probably notice this bug more frequently than others.
For instance, today, when I first loaded the page, it had all the 94 repositories in the filter. But then I reloaded the page and it went down to 87, which is a couple months old filter. Since I'm getting this bug quite frequently, I learned to copy the json from the Session Storage and keep it in a file to fix the issue immediately, but it's still annoying and I may not notice when the filters go down.
Since I fixed this version of the filters with the saved json, next time this bug happens, it will show me 94 when I actually have more than that.
My hypothesis is that you are saving this json in multiple places and only one is being saved at any given time when we hit save. Then, for some reason, the main save doesn't show up in the Session Storage and you show like a backup copy from an older save.
I should probably try to test my hypothesis before opening this issue, but if I'm wrong, you would know, so you could find a way to fix it anyway
To Reproduce Steps to reproduce the behavior:
Expected behavior Keep filters
Desktop (please complete the following information):