We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
目前alist的排序既有前端排序,又有后端排序。某些情况下两边会冲突,会打断用户的良好体验。
具体表现在,在后端设置好“文件夹提前”后,前端第一次加载的文件顺序是正确的,但是当用户点击按“名称、修改时间”排序的按钮后,就会走前端的排序逻辑,此时就不再是后端driver返回的顺序了。而且文件夹也会被打乱到文件中,后端的顺序就失效了,导致体验很不好。
希望后续能将排序工作全部交给后端做,前端每次修改排序方式时,都向后端请求一次文件列表,确保每次排序都是后端driver所返回的顺序。
个人感觉每次切换排序都发起一次请求所带来的开销仍在可接受范围里,和点击进入子目录一样,都是非常频繁的行为,应该不会对后端造成性能或者带宽上的压力。
No response
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Be sure to follow the issue template!
Sorry, something went wrong.
No branches or pull requests
Please make sure of the following things
Description of the feature / 需求描述
目前alist的排序既有前端排序,又有后端排序。某些情况下两边会冲突,会打断用户的良好体验。
具体表现在,在后端设置好“文件夹提前”后,前端第一次加载的文件顺序是正确的,但是当用户点击按“名称、修改时间”排序的按钮后,就会走前端的排序逻辑,此时就不再是后端driver返回的顺序了。而且文件夹也会被打乱到文件中,后端的顺序就失效了,导致体验很不好。
Suggested solution / 实现思路
希望后续能将排序工作全部交给后端做,前端每次修改排序方式时,都向后端请求一次文件列表,确保每次排序都是后端driver所返回的顺序。
个人感觉每次切换排序都发起一次请求所带来的开销仍在可接受范围里,和点击进入子目录一样,都是非常频繁的行为,应该不会对后端造成性能或者带宽上的压力。
Additional context / 附件
No response
The text was updated successfully, but these errors were encountered: