nuclide-file-tree bugs

[alicoding]

Hey guys!

First of all, thanks for the invitation and I'm happy to contribute and will do as much as I can.
I thought it'd be nice to file a meta bug for Nuclide's specific feature and reference them to any known bug, and I'm not sure if that's a good thing to do but if isn't the right workflow please feel free to close this bug and I will file a new bug for my issue that I've found.

• Two file/directory tree on sidebar - Opening a folder? #3
• Clicked on the item on the tree does not open the file right away (needs to double click to do so).
• Clicked on the folder does not expand the item.

So I'm not sure if they are intentional there for the last two?

[ssorallen]

Thanks for the issue.

The latter two are intentional in our file tree, but we are definitely interested in feedback. You can either expand a directory by clicking the arrow next to it or by first selecting the directory and then clicking again.

#3 is unintended, and we will look at merging the PR to prevent the second tree from displaying.

[enilsen16]

The popular file-icons package is also not supported by nuclide-file-tree.

[ssorallen]

Thanks for pointing that out, @enilsen16. That package looks to be relying on the file tree using the icon-file-text icon for all file types, but Nuclide's tree does some file type customization already. I'll open a separate issue to track that.

[steve-rodrigue]

I too have 2 file/directory tree like mentioned above

Ill update when you guys provide a patch. I'm very with nuclide so far, thanks!

[ssorallen]

'nuclide-file-tree' now permanently disables Atom's 'tree-view' package. If you disable 'nuclide-file-tree' via Atom's Settings view, 'nuclide-file-tree' will re-enable 'tree-view' (https://github.com/facebook/nuclide/blob/master/pkg/nuclide/file-tree/lib/main.js#L153). If you run Atom in safe mode you will have to manually re-enable 'tree-view' or remove it from disabledPackages in ~/.atom/config.cson.