Improve UX of Web IDE on shared branch
Problem to solve
Currently there are a number of issues that occur when commits are added on a branch that I'm working on. One example:
- User A opens Web IDE on
master
- User A edits a file "foo.js" to import and use "bar.js"
- Meanwhile, User B opens Web IDE on
master
- User B removes "bar.js"
- User B commits.
- User A is working on an old commit now, so "bar.js" is still visible.
- User A web terminal tests pass so they commit.
- User A's commit ends up breaking the pipeline and "bar.js" is still visible in User A's file tree because the tree and contents are cached.
☹
Proposal
There's a brute force fix for this (always resetting the IDE after commit + pinging user when commit is out of date), but I think we need to evaluate this from a holistic UX perspective.