Open HankG opened 6 years ago
I've tested this on the Mobile version coded in PR #7884 against Issue #7840 and the behavior is correct there (the code is all Rails versus Rails and JavaScript so the discrepancy is not necessarily surprising).
I tag this as a bug but with low priority imo.
I ran across this bug while testing a feature. On the desktop app toggling between ignoring a user and not does not preserve the correct state. When a user ignores/blocks another one any aspects they are in are removed. If I immediately undo the block without refreshing however it shows the original aspects the user was in. On refresh it shows the correct state. For example:
Before ignoring:
After ignoring:
After reverting the ignore but before refreshing:
After refresh:
I'm pretty sure I know how I'd change this to make it consistent, basically a change trigger is probably not being picked up along the way and causing the service populating the drop down to refresh correctly. I'm not actively working but if someone would like to add this to the #hacktoberfest this could be an interesting low hanging bug to pick up.