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
方案1:目前的useRequest能力还是比较弱的,可以参考ahooks的useRequest进行封装,轻量级且功能也比较强大。 方案2:理论上vue-request可以直接在uniapp中使用,直接替换成vue-reques的useRequest
useRequest
ahooks
vue-reques
The text was updated successfully, but these errors were encountered:
已经集成了vue-query,可以试用下是否更方便呢
Sorry, something went wrong.
我想 vue-query 和 useRequest他们的定位是不一样的。vue-query中的概念更多,更偏向于状态管理库,而useRequest看几分钟文档就能上手使用,上手几乎0成本,这里有一篇文章来对比它们的优势
vue-query
已经集成了vue-query,可以试用下是否更方便呢 我想 vue-query 和 useRequest他们的定位是不一样的。vue-query中的概念更多,更偏向于状态管理库,而useRequest看几分钟文档就能上手使用,上手几乎0成本,这里有一篇文章来对比它们的优势
可是就我们团队的使用经验来看,没有人把它当状态管理用,当然也可以兼顾接口状态管理的需求,但是我们更多的是把它当成useRequest来用,而且还可以方便的处理兄弟组件的视图互相刷新
vue-query 用好常用的两个query就能解决90%的业务问题,我会详细深入看一下他们的对比
No branches or pull requests
Feature request(新功能建议)
方案1:目前的
useRequest
能力还是比较弱的,可以参考ahooks
的useRequest
进行封装,轻量级且功能也比较强大。方案2:理论上vue-request可以直接在uniapp中使用,直接替换成
vue-reques
的useRequest
The text was updated successfully, but these errors were encountered: