You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
This was once used by notifyPathDeleted()'s call to notifyFileDeleted() (which then passes the flag along to closeFullEditor()). But now that notifyPathDeleted() simply delegates over to FileSyncManager.syncOpenDocuments(), nothing in our codebase calls either closeFullEditor() or notifyFileDeleted() with this flag.
We should either (a) decide it's definitely unneeded and remove it to reduce complexity, or (b) decide it still is needed and then figure out how it should be worked into FileSyncManager.
I'm not clear on why it was needed originally -- possibly just for efficiency? Or maybe reducing flicker in the case that many images were closed at once?
The text was updated successfully, but these errors were encountered:
This was once used by notifyPathDeleted()'s call to notifyFileDeleted() (which then passes the flag along to closeFullEditor()). But now that notifyPathDeleted() simply delegates over to FileSyncManager.syncOpenDocuments(), nothing in our codebase calls either closeFullEditor() or notifyFileDeleted() with this flag.
We should either (a) decide it's definitely unneeded and remove it to reduce complexity, or (b) decide it still is needed and then figure out how it should be worked into FileSyncManager.
I'm not clear on why it was needed originally -- possibly just for efficiency? Or maybe reducing flicker in the case that many images were closed at once?
The text was updated successfully, but these errors were encountered: