Is there an "agent" out there that auto solves lin...
# random
v
Is there an "agent" out there that auto solves linting problems for you? Copilot in vscode is nice for each individual issue, but I have ~30 linting errors with 90% of them being simple fixes that copilot can handle. Anyway to run copilot on all of these for you that anyone has played with? I can't believe I don't see a tool doing this already Output I want to feed in
Copy code
tap_mysql/client.py:45:9: D107 Missing docstring in `__init__`
tap_mysql/client.py:45:25: ANN002 Missing type annotation for `*args`
tap_mysql/client.py:45:33: ANN003 Missing type annotation for `**kwargs`
tap_mysql/client.py:55:89: E501 Line too long (100 > 88)
tap_mysql/client.py:60:89: E501 Line too long (110 > 88)
tap_mysql/client.py:64:89: E501 Line too long (162 > 88)
tap_mysql/client.py:68:89: E501 Line too long (119 > 88)
tap_mysql/client.py:202:9: PLR0913 Too many arguments in function definition (6 > 5)
tap_mysql/client.py:228:89: E501 Line too long (100 > 88)
tap_mysql/client.py:239:9: ERA001 Found commented-out code
tap_mysql/client.py:302:9: ANN201 Missing return type annotation for public function `get_sqlalchemy_type`
tap_mysql/client.py:302:35: ANN001 Missing type annotation for function argument `col_meta_type`
tap_mysql/client.py:318:17: G004 Logging statement uses f-string
tap_mysql/client.py:318:89: E501 Line too long (96 > 88)
tap_mysql/client.py:332:17: RET505 Unnecessary `else` after `return` statement
tap_mysql/client.py:335:13: TRY400 Use `logging.exception` instead of `logging.error`
tap_mysql/client.py:335:31: G004 Logging statement uses f-string
tap_mysql/client.py:336:19: TRY201 Use `raise` without specifying exception name
tap_mysql/client.py:356:89: E501 Line too long (102 > 88)
tap_mysql/client.py:426:14: SLF001 Private member accessed: `_connect`
tap_mysql/tap.py:38:9: S101 Use of `assert` detected
tap_mysql/tap.py:94:89: E501 Line too long (199 > 88)
tap_mysql/tap.py:102:89: E501 Line too long (212 > 88)