We've been using new Tree View API to provide structured view of F# projects - in F# project files needs to be ordered according to compilation order so this additional view gives users better information about their project. We also include in the view list of project references, and assembly references so it's really similar to the Visual Studio solution explorer.
It looks like following:

As I've mentioned - ordering of files is really important for the F# projects, and we provide couple of helper commands to manage it (move file up/down etc). Those commands work more or less, but I don't think it's best UX.
I think it would be super nice if users had ability to use normal drag and drop to manipulate the order - just as they are able to manipulate files in normal file explorer (drag and drop files to move them to subfolder for example)
Just to add weight to this: file ordering is critically important for F# users. We're also exploring adding click and drag for CPS in Visual Studio, which would leave VSCode as the only F# editor that doesn't support click and drag for file ordering.
Oh that would be an awesome feature!
馃挴 * 馃憤
+1
+1
That would be a really helpful feature.
+1
This would be awesome. Some things are actually better done with a GUI and this is one.
+1
F# developers need this feature as an air.
馃挴
+1
I'd like to see this too for a UI tree we're building. Some things it'd be nice for the API to support:
Someone wrote that we need to wait for the vscode team to implement the feature. Does that mean that we should not fork the repo and try to implement it? Because that that is not their process and a pull request would be rejected? Thank you.
any update about this requirement?
No plans yet.
Is this still considered? It would be a great addition to simplify a lot of UI workarounds for TreeViews.
Relatedly, it would also be great to enable dragging from a tree view into an editor, especially a custom editor. This would enable tree views to provide snippets, components, colors, etc.
Are there any plans for implementing this in the near future?
Most helpful comment
Is this still considered? It would be a great addition to simplify a lot of UI workarounds for TreeViews.