From 64e92ca6a14a4778c7801ee2b5625e0b89727f5d Mon Sep 17 00:00:00 2001 From: Derek Pollard Date: Thu, 1 Oct 2020 11:33:13 -0500 Subject: [PATCH] fix: textlint bug causing PR's to fail checks fix #2636 (#2637) --- packages/docs/docs/miscellaneous/design-concepts.md | 4 ++-- packages/docs/package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/packages/docs/docs/miscellaneous/design-concepts.md b/packages/docs/docs/miscellaneous/design-concepts.md index 05ecd00262..f07ad651f4 100644 --- a/packages/docs/docs/miscellaneous/design-concepts.md +++ b/packages/docs/docs/miscellaneous/design-concepts.md @@ -16,11 +16,11 @@ VuePress 1.0 has been rewritten extensively, and the most important one is the i ### Decoupling -With plugins, we can implement many of the core functions with plugins, and you can see many built-in plugins [here](https://github.com/vuejs/vuepress/tree/master/packages/%40vuepress/core/lib/node/internal-plugins) that cover many of the core functions of VuePress, which used to blend in all parts of the code base, but now they’re clear at a glance. +With plugins, we can implement many of the core functions with plugins, and you can see many built-in plugins [here](https://github.com/vuejs/vuepress/tree/master/packages/%40vuepress/core/lib/node/internal-plugins) that cover many of the core functions of VuePress, which used to blend in all parts of the codebase, but now they’re clear at a glance. ### Configuration management -In the past, when we came across some less common requirements, we had some doubts: if we wanted to not support it, VuePress usage scenarios were limited; but if we wanted to support it, we had to write it into the core code base and set up a separate configuration API for it. For the maintainers, apart from not conducive to long-term maintenance, this sometimes makes us feel exhausted. We must think of some better solutions. Yes, this is plugin. +In the past, when we came across some less common requirements, we had some doubts: if we wanted to not support it, VuePress usage scenarios were limited; but if we wanted to support it, we had to write it into the core codebase and set up a separate configuration API for it. For the maintainers, apart from not conducive to long-term maintenance, this sometimes makes us feel exhausted. We must think of some better solutions. Yes, this is plugin. ### `.vuepress/config.js` is also a plugin diff --git a/packages/docs/package.json b/packages/docs/package.json index 19f1c0f987..23d0c33504 100644 --- a/packages/docs/package.json +++ b/packages/docs/package.json @@ -45,7 +45,7 @@ "textlint-rule-diacritics": "^1.0.0", "textlint-rule-en-capitalization": "^2.0.2", "textlint-rule-stop-words": "^1.0.17", - "textlint-rule-terminology": "^1.1.30", + "textlint-rule-terminology": "^2.1.4", "textlint-rule-write-good": "^1.6.2", "vue-toasted": "^1.1.25", "vuepress": "1.6.0",