Please make Files view show links to folders as well as actual folders

[threed-factory-store]

I'm using the MicroPython Editor on Linux. I'd like to have a "lib" folder that is shared between projects.

I can create a "lib" folder under one project, and the Files view will show it with the other files in that project.

But if I add a link to a "lib" folder somewhere else, the Files view does not include that folder.

And, of course, files in the "lib" folder should be copied to the Arduino when the other project files are copied.

[ubidefeo]

@threed-factory-store
could you explain this better?
do you mean sym-link?

sym-links are not resolved, and the way you do this in MicroPython is to upload your modules/packages to the board's /lib (or /flash/lib for STM32 and other platforms).
Once they are there, they are resolved by every .py file importing them correctly

[threed-factory-store]

Hmm...I replied to the email I received about this, but it isn't showing up here so here it is:

I mean when MicroPython shows you a list of files on your computer, it should include sub-folders so you can open a file in a sub-folder of your project. When I upload files to the board, it should include files in the sub-folders. I think it already does all this.

I have multiple projects and I would like to share some files between them. One way to do this would be to create a shared folder on my computer, then create a link in my project folder that resolves to the shared folder. I suppose I could manually upload my shared files to the /lib folder on the board, but I'd really rather not have another step to do.

[ubidefeo]

Then I think you want to resolve symbolic links.
I think this would be possible, but I have one case against this and it's due to the fact that upload from computer to board is unfortunately very slow in this editor. Every time we try to speed it up we break the upload for slower boards.

If you have a symlinked folder in multiple projects and you keep adding modules to the source folder, you may end up taking a long time to upload every project with that folder linked into itself, no matter what the real needs of this project are.
The way to make this work is, as you guessed, to upload the shared libraries to /lib (or /flash/lib on some boards).
You may also have the need to have a single project use a different version of a module, and that's when you want to upload it somewhere else it can be sourced from the board (but import paths can turn into a nightmare with packages).

What I do with my students is asking them to create a lib folder inside the local machine's editor's folder, and that's where they keep the libraries downloaded and upload them to /lib when they need to use them (they are safe there).

Of course you may want to use a sym-link for this folder too, and it makes a lot of sense.

So while I am a bit against the way it would work resolving and uploading sym-linked resources, I can see the appeal having a sym-link folder as the local folder's lib from where to quickly access things.

I'm gonna look into it, but priority is quite low, since we have a few more bugs to address first.
Appreciate the report, gonna mark this as feature request.

Thank you :)