Skip to content
New issue

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

Drop flake8 but keep using pydoclint #4235

Merged
merged 4 commits into from
Jun 25, 2024
Merged

Drop flake8 but keep using pydoclint #4235

merged 4 commits into from
Jun 25, 2024

Conversation

Qalthos
Copy link
Collaborator

@Qalthos Qalthos commented Jun 25, 2024

This works around a new feature in pydoclint that adds new checks by default

@ssbarnea ssbarnea changed the title Update pre-commit Drop flake8 but keep using pydoclint Jun 25, 2024
@ssbarnea ssbarnea merged commit 4e5d02b into main Jun 25, 2024
12 of 14 checks passed
@ssbarnea ssbarnea deleted the chore/pydoclint-0.5.0 branch June 25, 2024 17:35
cidrblock added a commit that referenced this pull request Jun 26, 2024
Since flake8 has been removed, VsCode no longer provided feedback during
devleopment about new docstring errors.

This PR add a new task called `pydoclint` that runs pydoclint in the
background. Message from pydoclint are parsed with a regex and presented
in the problems tab of VsCode by the task.

VsCode does not have native support fdor running a task on save, so a
new extension is added to support that.

The flake8 extension is removed which was an oversight in #4235 

Related #4236
cidrblock added a commit that referenced this pull request Jun 26, 2024
- finish removing flake8
- update constraints after flake8 removal
- update pydoclint config and update baseline
Followup work from #4241 and #4235
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants