I've tried a lot of things to make the URL look nice but somehow there's
always a bug to handle all possible scenarios. Eg:
/test/test#test%20with a: space.txt
maybe one day, we can make the urls looks nicer but this would need a
significant revamp, until that happen, that will do.
tip: don't understimate the work it takes to do it nicely, I've tried to
do this 2 times quickly and everytime there's a edge case that make
things not working and breaking other odd stuff
until this, if a user tries to connect to the same backend with a
different path, the frontend would flicker as we'd get things from the
wrong cache key
until this, if a user tries to connect to the same backend with a
different path, the frontend would flicker as we'd get things from the
wrong cache key
we used to have the readonly attribute but somehow it's not supported by
all fields, eg: select. As such when something is read only we disable
the field
before this commit, the issue was:
1. whenever uploading a large folder, any upload would trigger the ls change, resulting in a lot of unecessary dom
changes which in case the user is browsing through a lot of picture would trigger some flickering in the thumbnail.
2. large upload would be slow as virtual.before would call change
detection and refresh the list of files within the folder constantly
now by avoiding mutations we effectively just rerender when something we
are interested changes: aka something change in the current folder the
user is in
this fix a panic that can be replicated using the video thumbnail
plugin, opening up a page with a lot of videos. Under the hood, the
server would call ffmpeg that would make a bunch of HTTP range requests
that would call the cache concurrently, hence causing the panic
up until now, the stance was to refuse video thumbnail because it's too
slow but really many people don't seem to care that much about it and
keep insisting to have it.
With this solution, it's not in the base build but it gives an
option for those people to make it happen
