-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Conversation
okay, I'm going to make my changes in this PR now. Thanks for going through all this pain merging master with your branch. |
The DOM structure has changed a little in the tree.
This was very hard to track down because our promises and event handlers swallowed an exception thrown in FileTreeViewModel.
The project files cache was not being cleared on every file system change, as it had been previously. Also removed duplicate projectClose event.
…s opening files from working set
@dangoor Apparently, we need to set |
…to ProjectManager
…ed errors opening files from working set" This reverts commit 83b95c4.
…for top-level directories, but not for subdirectories yet (see failing test)
I'm seeing this error when I launch Brackets:
Not sure if that happens on master. |
* @param {Array.<File>=} additionalFiles Additional files to include (for example, the WorkingSet) | ||
* Only adds files that are *not* under the project root or untitled documents. | ||
* | ||
* @return {$.Promise} Promise that is resolved with an Array of File objects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: everywhere in this file we are referring to jQuery.Promise instead of $.Promise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both are in use in the code... $.Promise
seems to be in the lead with 180 matches vs. 70 matches for jQuery.Promise
. Maybe I'll just switch them all to $.Promise
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By which I mean switch all of them in the new ProjectManager files
@dangoor yes, I see this error too. And yes, I still can't comment on ProjectManager.js. |
Hey @dangoor, here is my list of comments for
General:
|
I tried replacing the |
I'm eager to see their answer. |
No word from the React people, so I've gone ahead and documented |
@ingorichter Are you fine with my proposed behavior for control-alt-click?
I think this is more consistent than the old behavior, even if it's not 100% consistent. (Opening all children could potentially freeze up Brackets if you've got a lot of files...) |
Regarding your comments about ProjectManager.js:
|
Changes pushed. |
Also turn on es5 mode for JSLint and JSHint so we can call .delete directly. We wouldn't support any non-es5 browsers anyhow.
@dangoor I'm okay with your changes to the control+alt+click behavior. |
I think the travis failure needs to be fixed before we can merge it into master. |
Grr... that's really annoying. JSHint is complaining about a JSLint option. |
OK, found a combo that makes both JSHint and JSLint happy. |
@ingorichter since it sounds like you're ready to merge into master, I won't make any more changes on the branch. I'll target additional bug fixes from this point against master. |
Thanks @dangoor. Merged. |
This is an updated/rebased ProjectManager revamp for #8788. This replaces #8885.
cc @ingorichter
Here's my current list of issues/things to test that I'm looking into:
ProjectModel._selections
selectIfVisible
the old code looks at whether the current doc has become visible.curDoc = DocumentManager.getCurrentDocument();
and thenif (_hasFileSelectionFocus() && curDoc && data)
ProjectManager.showInTree
needs to expand nodes and not do anything if the path is outside the project or doesn't existProjectManager.refreshFileTree
needs to make sure it doesn't run multiple times and has the 1 second delay between runs if there's one pending. Also double check that it's returning a promise that's resolved when it's done.