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
Starting in Sprint 36, I believe you can remove your extension's explicit calls to ProjectManager.refreshFileTree(). Brackets will automatically detect filesystem changes (including changes made by a different process), and it will update the tree incrementally without any need for a full refresh.
You should be able to invoke the FILE_ADD_TO_WORKING_SET command at any time -- no need to wait for the project tree to redraw (that is, the "selectionRedraw" stuff in your code can be removed too).
You can release an update to the extension at any point with "brackets": ">=0.36.0" in your package.json file; any users who are still on older versions of Brackets will simply be directed to install an older version of your extension.
The text was updated successfully, but these errors were encountered:
Starting in Sprint 36, I believe you can remove your extension's explicit calls to
ProjectManager.refreshFileTree()
. Brackets will automatically detect filesystem changes (including changes made by a different process), and it will update the tree incrementally without any need for a full refresh.You should be able to invoke the
FILE_ADD_TO_WORKING_SET
command at any time -- no need to wait for the project tree to redraw (that is, the"selectionRedraw"
stuff in your code can be removed too).You can release an update to the extension at any point with
"brackets": ">=0.36.0"
in your package.json file; any users who are still on older versions of Brackets will simply be directed to install an older version of your extension.The text was updated successfully, but these errors were encountered: