Closed ranfdev closed 3 years ago
I understand being able to switch accounts from everywhere can be useful, but it's just not possible, unless you map the IDs between instances (but I have no idea on how to implement this).
There's no need to use IDs. Account and status entities contain the url
field which can be resolved by the instance (confirmed to work through the Search view).
To implement this behavior, all it would take is introduce an invalidation mechanism that checks if the instance has changed, ask the new instance to resolve the entity by its url
, and replace the old entity with the response.
Problem: If you switch account inside views requiring instance-specific IDs, everything breaks: sometimes inconsistent data will be loaded, sometimes nothing can be loaded at all, because the corresponding ID in the new instance doesn't exist.
How to reproduce: Steps to reproduce the behavior:
Screenshots: Before switching account (everything is correct here): After switching accounts: