Skip to content

Commit

Permalink
...
Browse files Browse the repository at this point in the history
  • Loading branch information
wendux committed Feb 10, 2023
1 parent ac78e61 commit a6fc5e1
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 2 additions & 4 deletions README-ZH.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,6 @@
> 重要提醒:很遗憾的跟大家宣布一件事:**后续我(@wendux)将不能继续维护dio库**。我明白dio作为一个广受欢迎的Http请求库,拥有有大量的用户,且基于dio已经形成了一定规模的插件生态,但由于dart/flutter的更新速度较快加之我个人精力实在有限,放弃维护对我来说是一个不得已的决定,所幸dio经过4个大版本的迭代,整个核心和架构已经相对稳定,二次开发的难度不大,大家可以在最新版源码基础上进行fork后进行定制开发。

文档语言: [English](https://github.com/flutterchina/dio) | [English](README.md)

> 中文文档更新会较慢,请优先查看英文文档 [English](README.md)
文档语言: [English](https://github.com/flutterchina/dio)

# dio

Expand Down
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
Language: [English](README.md) | [中文简体](README-ZH.md)
> Important note: I'm sorry to announce one thing to you: **I (*@ wendux*) will not be able to continue to maintain the dio library** . I understand that as a popular Http request library, dio has a large number of users, and has formed a plug-in ecosystem of a certain scale based on dio. However, due to the fast update speed of dart/flutter and my limited personal energy, it is an unavoidable decision for me to give up maintenance.
>
> Fortunately, after the iteration of four major versions, the whole core and architecture of dio has been relatively stable, and the secondary development is not difficult. You can make customized development after forking on the basis of the latest version of source code.
# dio
# dio [中文简体](README-ZH.md)
[![Pub](https://img.shields.io/pub/v/dio.svg?style=flat-square)](https://pub.dartlang.org/packages/dio)
[![support](https://img.shields.io/badge/platform-flutter%7Cflutter%20web%7Cdart%20vm-ff69b4.svg?style=flat-square)](https://github.com/flutterchina/dio)

Expand Down

0 comments on commit a6fc5e1

Please sign in to comment.