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
因为树组件,用于类似部门选择的话一般数据很有很多级的,一次性查找太慢
The text was updated successfully, but these errors were encountered:
赞同楼上的~~
Sorry, something went wrong.
@sky875576452 前端搜索还是不算慢的,你说的慢是后台返回慢吧? 我们这边给数据做了Gzip压缩,1M的数据变成了300k,然后加了一个小时的缓存,让后端去除了多余的字段,体验还好。
为什么没有做异步加载的原因是,我这边的搜索是前端搜索,没有做后端的搜索,如果是异步加载的话,用户搜索不到没有加载出来的节点。
个人目前暂时没有时间去做异步加载。。。连续加班两月了== 建议fork下然后组装自己想要的功能,会更小巧顺手,大而全的组件最后会变得性能不是很好。
我赞同作者的方法。懒加载会扯出很多问题。
No branches or pull requests
因为树组件,用于类似部门选择的话一般数据很有很多级的,一次性查找太慢
The text was updated successfully, but these errors were encountered: