Describe the bug
If you are authenticated and create a collection, and then log out, the collection will still show up in the Collections popover. It should not show up anymore if you are logged out.
If you then sign in again and then sign back out, the collection no longer shows up in the popover. So signing in/out clears the local cache, but there is something going on when you first create a collection while authenticated that is making the collection stay in the local cache (in indexedDB).
To Reproduce
Steps to reproduce the behavior:
Log in
Create a collection
Sign out
Click on the "Collections" tab in the side bar to open the popover. The collection you just created will be there. It shouldn't be there if we're logged out!
Log in again
Sign back out
Click on the "Collections" tab in the sidebar. The collection is now gone (as it should be).
See error
Expected behavior
The collections we create while authenticated should only be seen while we are authenticated! When logged out they should not be showing up.
Screenshots
n/a
Desktop (please complete the following information):
Describe the bug If you are authenticated and create a collection, and then log out, the collection will still show up in the Collections popover. It should not show up anymore if you are logged out.
If you then sign in again and then sign back out, the collection no longer shows up in the popover. So signing in/out clears the local cache, but there is something going on when you first create a collection while authenticated that is making the collection stay in the local cache (in indexedDB).
To Reproduce Steps to reproduce the behavior:
Expected behavior The collections we create while authenticated should only be seen while we are authenticated! When logged out they should not be showing up.
Screenshots n/a
Desktop (please complete the following information):
Additional context n/a