Document how to test plugins

从现有的 plugin-development/formatters 文档以及 issue 中描述的 flake8 2.x 到 3.x 迁移背景开始。记录一个完整示例，涵盖有效的函数或类入口点、针对一项检查测试字符串，以及不使用子进程运行标准检查。示例回答全部三个问题并适合用于文档 PR，即视为完成。

In GitLab by @stephenfin on May 23, 2019, 03:07

I'm trying to migrate hacking from flake8 2.x to 3.x and finding it extremely difficult to do so because the internals of the flake8 have changed so drastically between these versions (plus hacking does some stuff that's too smart for its own good, IMO). The flake8 documentation provides some introductory text on plugins, including a guide on writing a "formatting type" plugin (though it doesn't explain what a formatting plugin actually is...) but there's nothing about testing this or even what type of class or function the entrypoints should point to. The biggest issue I have is that I want to run flake8 in it entirety (i.e. with both the standard checks and my plugin enabled) on a test string, but there doesn't appear to be anyway to do this.

Would it be possible to get a small worked example that demonstrates:

What the entrypoint should look like (i.e. if it can be a Python function, a class, or both)
How you can test a string against only a single check
How you can test a string against flake8's standard checks (without having to resort to a subprocess call)

I'll happily submit a documentation PR based on this example, if it would be helpful.

Document how to test plugins

评估

调研方向

描述

环境准备

从这里开始

PyCQA/flake8 的其他 Issue

相似的 Issue

Document how to test plugins

哪里不对？

评估

调研方向

描述

环境准备

从这里开始

PyCQA/flake8 的其他 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

相似的 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

把新 issue 发到你的邮箱