#linters — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #linters, aggregated by home.social.
-
🚀 Ah yes, the "good old days" when formatting was a mythical beast slain by the divine compiler gods of the 80s. 🙄 Apparently, we're all just stuck in a time warp of linter debates while the ancients enjoyed their IR utopia. 🤯 Maybe we should just take a time machine back to when code formatted itself and we all rode dinosaurs to work! 🦖✨
https://maxleiter.com/blog/formatting #codinghumor #nostalgia #linters #timewarp #devlife #HackerNews #ngated -
Having access to fast internet is nice (100Gbs) but I am looking forward to a gig fiber provider coming to my neighborhood. This 75GB download would have been finished sooner.
Yesterday was so nice in that I got to write some bash scripts. Are there any linters for bash scripts that folks recommend?
https://aronwarren.com/2024/12/08/100daystooffload-23-100-2/
-
Having access to fast internet is nice (100Gbs) but I am looking forward to a gig fiber provider coming to my neighborhood. This 75GB download would have been finished sooner.
Yesterday was so nice in that I got to write some bash scripts. Are there any linters for bash scripts that folks recommend?
-
PSA: Today I learned about `chktex`... something like 19 years after having started using \(LaTeX\). At least now I know it is there, and the different warning types are very useful…
In particular, Warning 17 (mismatch in number of parenthesis, square brackets, or curly braces), Warning 10 (solo parenthesis, bracket or brace found), and Warning 9 (expected itemize, found document).
Update: I have also just learned about `lacheck`, which gives you a different perspective... and seem to prefer for what I am doing right now.
#PSA #TIL #PublicServiceAnnouncement #TodayILearned #LaTeX #linters #chktex #lacheck #CLI
-
🛠️🚀 Excited for James Conroy's upcoming talk on Automated Code Review! Learn how #Linters, #StaticTesting, & more can transform your code base and enhance your #CICD pipeline. Mark your calendars! #SLUUG https://www.meetup.com/saint-louis-unix-users-group/events/302045023/
-
🛠️🚀 Excited for James Conroy's upcoming talk on Automated Code Review! Learn how #Linters, #StaticTesting, & more can transform your code base and enhance your #CICD pipeline. Mark your calendars! #SLUUG https://www.meetup.com/saint-louis-unix-users-group/events/302045023/
-
Улучшаем python код в пару кликов
Разрабатывая огромные проекты в команде сталкиваешься с проблемой, что люди не понимают друг друга, и каждый пишет в своей стилистике. Поэтому в дальнейшем будет трудно поддерживать этот код В статье научимся писать код в единой стилистике и даже делать это автоматически. Улучшать проекты!
-
Топ 5 продвинутых инструментов Data Scinece. Изучи за выходные и будешь выделяться
Привет, чемпионы! Сегодня рассмотрим, как облегчить себе жизнь, применяя 5 инструментов в своих проектах. Эти инструменты улучшат ваш код, сделают ваш pipeline более стабильным и позволят не писать один код по 10 раз. Круто? Погнали! Изучать новое!
-
Топ 5 продвинутых инструментов Data Scinece. Изучи за выходные и будешь выделяться
Привет, чемпионы! Сегодня рассмотрим, как облегчить себе жизнь, применяя 5 инструментов в своих проектах. Эти инструменты улучшат ваш код, сделают ваш pipeline более стабильным и позволят не писать один код по 10 раз. Круто? Погнали! Изучать новое!
-
Топ 5 продвинутых инструментов Data Scinece. Изучи за выходные и будешь выделяться
Привет, чемпионы! Сегодня рассмотрим, как облегчить себе жизнь, применяя 5 инструментов в своих проектах. Эти инструменты улучшат ваш код, сделают ваш pipeline более стабильным и позволят не писать один код по 10 раз. Круто? Погнали! Изучать новое!
-
I've made a Python :python: code linting Action ▶️ for GitHub :github: Code Scanning.
It wraps up #Ruff, #Flake8, #Pylint, #Fixit2, #Mypy, #Pyright and #Pytype into an Action that uploads to Code Scanning, part of Advanced Security, the GitHub appsec platform.
ℹ️ that’s free for open source repos hosted on GitHub!
Read 📖 about it👇 on my blog:
https://lnkd.in/es_pd2W6Try ⚙️ it👇 on the Actions ▶️ marketplace:
https://lnkd.in/ei7-H2V9#Python #Linting #CodeQuality #Linters #SARIF #GitHubActions
-
I've made a Python :python: code linting Action ▶️ for GitHub :github: Code Scanning.
It wraps up #Ruff, #Flake8, #Pylint, #Fixit2, #Mypy, #Pyright and #Pytype into an Action that uploads to Code Scanning, part of Advanced Security, the GitHub appsec platform.
ℹ️ that’s free for open source repos hosted on GitHub!
Read 📖 about it👇 on my blog:
https://lnkd.in/es_pd2W6Try ⚙️ it👇 on the Actions ▶️ marketplace:
https://lnkd.in/ei7-H2V9#Python #Linting #CodeQuality #Linters #SARIF #GitHubActions
-
I've made a Python :python: code linting Action ▶️ for GitHub :github: Code Scanning.
It wraps up #Ruff, #Flake8, #Pylint, #Fixit2, #Mypy, #Pyright and #Pytype into an Action that uploads to Code Scanning, part of Advanced Security, the GitHub appsec platform.
ℹ️ that’s free for open source repos hosted on GitHub!
Read 📖 about it👇 on my blog:
https://lnkd.in/es_pd2W6Try ⚙️ it👇 on the Actions ▶️ marketplace:
https://lnkd.in/ei7-H2V9#Python #Linting #CodeQuality #Linters #SARIF #GitHubActions
-
I've made a Python :python: code linting Action ▶️ for GitHub :github: Code Scanning.
It wraps up #Ruff, #Flake8, #Pylint, #Fixit2, #Mypy, #Pyright and #Pytype into an Action that uploads to Code Scanning, part of Advanced Security, the GitHub appsec platform.
ℹ️ that’s free for open source repos hosted on GitHub!
Read 📖 about it👇 on my blog:
https://lnkd.in/es_pd2W6Try ⚙️ it👇 on the Actions ▶️ marketplace:
https://lnkd.in/ei7-H2V9#Python #Linting #CodeQuality #Linters #SARIF #GitHubActions
-
I've made a Python :python: code linting Action ▶️ for GitHub :github: Code Scanning.
It wraps up #Ruff, #Flake8, #Pylint, #Fixit2, #Mypy, #Pyright and #Pytype into an Action that uploads to Code Scanning, part of Advanced Security, the GitHub appsec platform.
ℹ️ that’s free for open source repos hosted on GitHub!
Read 📖 about it👇 on my blog:
https://lnkd.in/es_pd2W6Try ⚙️ it👇 on the Actions ▶️ marketplace:
https://lnkd.in/ei7-H2V9#Python #Linting #CodeQuality #Linters #SARIF #GitHubActions
-
If your #git #repository runs #automatedTests or #linters #precommit or #prepush I WILL --no-verify that shit *everytime*
#software #programming #huskey #husky #github #commit #webdev #softwaredevelopment #testing
-
If your #git #repository runs #automatedTests or #linters #precommit or #prepush I WILL --no-verify that shit *everytime*
#software #programming #huskey #husky #github #commit #webdev #softwaredevelopment #testing
-
If your #git #repository runs #automatedTests or #linters #precommit or #prepush I WILL --no-verify that shit *everytime*
#software #programming #huskey #husky #github #commit #webdev #softwaredevelopment #testing
-
If your #git #repository runs #automatedTests or #linters #precommit or #prepush I WILL --no-verify that shit *everytime*
#software #programming #huskey #husky #github #commit #webdev #softwaredevelopment #testing
-
If your #git #repository runs #automatedTests or #linters #precommit or #prepush I WILL --no-verify that shit *everytime*
#software #programming #huskey #husky #github #commit #webdev #softwaredevelopment #testing
-
#programming #linters #testing #test_coverage #bad_programming_habits
An observation about writing tests in weakly typed languages like Python.
You should DISABLE some linting features when writing tests. Not everywhere and not all of them. But where needed.
Lint being fully enabled for writing tests can guide you to fragile code and poor tests without realizing it because you may avoid writing tests that the linter complains about without thinking about WHY it's a lint issue and not a compiler error.
Linters catch problems that DO NOT violate the compiler's rules. Such as passing a wrongly typed value in a weakly typed language.
That is WHY they're lint issues rather than compiler errors: The compiler DOES NOT CARE if you do a bad thing that a linter complains about.
100% test coverage only proves you CAN execute all the code without generating unexpected results, not that it WILL always do the right thing for unexpected inputs and situations.
It only proves code functionality, NOT code correctness.
-
#programming #linters #testing #test_coverage #bad_programming_habits
An observation about writing tests in weakly typed languages like Python.
You should DISABLE some linting features when writing tests. Not everywhere and not all of them. But where needed.
Lint being fully enabled for writing tests can guide you to fragile code and poor tests without realizing it because you may avoid writing tests that the linter complains about without thinking about WHY it's a lint issue and not a compiler error.
Linters catch problems that DO NOT violate the compiler's rules. Such as passing a wrongly typed value in a weakly typed language.
That is WHY they're lint issues rather than compiler errors: The compiler DOES NOT CARE if you do a bad thing that a linter complains about.
100% test coverage only proves you CAN execute all the code without generating unexpected results, not that it WILL always do the right thing for unexpected inputs and situations.
It only proves code functionality, NOT code correctness.
-
#programming #linters #testing #test_coverage #bad_programming_habits
An observation about writing tests in weakly typed languages like Python.
You should DISABLE some linting features when writing tests. Not everywhere and not all of them. But where needed.
Lint being fully enabled for writing tests can guide you to fragile code and poor tests without realizing it because you may avoid writing tests that the linter complains about without thinking about WHY it's a lint issue and not a compiler error.
Linters catch problems that DO NOT violate the compiler's rules. Such as passing a wrongly typed value in a weakly typed language.
That is WHY they're lint issues rather than compiler errors: The compiler DOES NOT CARE if you do a bad thing that a linter complains about.
100% test coverage only proves you CAN execute all the code without generating unexpected results, not that it WILL always do the right thing for unexpected inputs and situations.
It only proves code functionality, NOT code correctness.
