There’s a saying that goes like: “If it ain’t broke, don’t fix it“. As a programmer, I’ve changed that to: “If it ain’t broke, break it then fix it” and that’s exactly what I did. While trying to “break” Thimble, I noticed that I’m able to create/rename folder and file and give it a name which includes a relative path(Like
What does that do? Well, In UNIX,
.. means parent directory of the current directory, so in this case, I’m creating a file named
file1 and placing it 2 folders up from the current directory. In Thimble, this is somewhat safe to do (Since file/folder structures are stored locally) but this is still a bug that could potentially lead to unwanted actions. Because Thimble is a fork of Adobe Brackets, it would be best to fix this issue in Brackets rather than on Thimble. Why? Because if any other projects are forked from Brackets (Like Thimble), it’s safe to assume they will also have this bug in it. Fixing it in Brackets ensures that other forks will eventually inherit the fix.
It seems that this bug was previously fixed(adobe#11862) but it was either reintroduced or it didn’t fully fix the issue. So I decided to make this one of the bug fixes I’m working on for release 0.2
My second bug is more of a feature. At the current state, there’s no way for the end-user to download a single file or whole folder structure.
If you want to download a single file/folder you need to download the whole project. It’s quite annoying and I decided to implement this feature (thimble#596)
Fixing these bugs shouldn’t take long. Hopefully.