New #Regal release is out! v0.8.0 brings a bunch of new features and improvements to your favorite #Rego linter, including a #GitHub output format which will annotate PRs with linter violations. Also four new #linter rules to catch both issues as well as non-idiomatic coding style. Check it out!

#OPA #OpenPolicyAgent #DevOps #DevSecOps #Development

https://github.com/StyraInc/regal/releases/tag/v0.8.0

@gdd @cst1

#tinytapeout For some reason, the Verilator #linter used in the GitHub actions doesn't know about the Sky130 standard cells. However, I do directly instantiate some inverter cells in my ring oscillator TRNG design.

Consequence: the action fails because the linter raises an error.

Solution? Disable the linter.

#hardware #vlsi #badprogrammer #computerscience

I'll be live coding in just about half an hour! Join me, and watch (or help!) me build a real-world linter for #golang.

https://youtube.com/live/nnrG7RfPbz0

#livestream #youtube #livecoding #linter #staticanalysis #coding

Today's my first day trying #deno.

Not sure how I feel about the built in #linter and formatter yet; me and #prettier are besties, and I have gotten used to #eslint

Still gonna give it a try.

#webDev #nodejs #node #npm #npmjs #javaScript #programming #code #dependencies

New blog just dropped! On using a #linter as a tool for learning a new #programming language, and how I tried to apply some of those ideas while building #Regal, the new linter for #Rego.

https://www.styra.com/blog/guarding-the-guardrails-introducing-regal-the-rego-linter/

#OpenPolicyAgent #OPA #CloudNative #CNCF #PolicyAsCode

Announced yesterday, Regal is a new linter for #Rego, with the ambitious goal of both catching bugs/mistakes in policy code, *and* to help people learn the language! If you ever work with #OPA, I’m sure you’ll find it useful. Check it out, and if you’d like to help kick-start the project by giving at star ⭐️ I’d be overjoyed!

https://github.com/StyraInc/regal/

#CloudNative #Linter #Code #Development #Co

#Vale describes itself as a “syntax-aware #linter for prose built with speed and extensibility in mind”. My overlay now has the latest v2.24.4 release available for fellow #Gentoo users.

I recommend previous users to continue reading about ebuild changes: https://blog.ferki.it/2023/04/25/packaging-vale-2-24-4-for-gentoo/

#Linter et #Lintian font partie des nouveaux venus dans le #MédiaWiki.

@+ !

TypL
The Type #linter for #javascript

https://medium.com/@lxmarinkovic/typl-the-type-linter-for-javascript-673e8f842c2d?source=friends_link&sk=4cc5d72eb8e076c9bd82455fc767e76f

`import {MyQueryDocument} from myQuery.graphql` with strict TS checks on @apollo/client `useQuery` and `client.query()` on node app is another challenge beaten this week.

No docs or reference implementation, so have to be inventive on #linter, #typescript, #codegen config

For curious: the key is to generate `myQuery.graphql.ts` by codegen near-operation-file. works perfect in React app, in
#oclif app have to trick with

`import {MyQueryDocument} from myQuery.graphql-generated`

Yesterday I've published a video showing how to use linters for Common Lisp code.

I talk about SBLint and Lisp Critic.

YouTube: https://www.youtube.com/watch?v=set7F0cfIs8
Fediverse: https://diode.zone/w/e1fXcRys3S3YcjVBnrjjw4

#commonlisp #lisp #codequality #linter

#python #linter #ruff #rust

- https://beta.ruff.rs/docs/
- https://notes.crmarsh.com/python-tooling-could-be-much-much-faster

ruff => An extremely fast Python linter, written in Rust.

Linting the CPython codebase from scratch.

⚡️ 10-100x faster than existing linters
🐍 Installable via pip
🛠️ pyproject.toml support
📦 Built-in caching, to avoid re-analyzing unchanged files
🔧 Autofix support, for automatic error correction (e.g., automatically remove unused imports)
📏 Over 400 built-in rules (and growing)
⚖️ Near-parity with the built-in Flake8 rule set
🔌 Native re-implementations of dozens of Flake8 plugins, like flake8-bugbear
⌨️ First-party editor integrations for VS Code and more
🌎 Monorepo-friendly, with hierarchical and cascading configuration

Ruff aims to be orders of magnitude faster than alternative tools while integrating more functionality behind a single, common interface.

Ruff can be used to replace Flake8 (plus dozens of plugins), isort, pydocstyle, yesqa, eradicate, pyupgrade, and autoflake, all while executing tens or hundreds of times faster than any individual tool.

It's a good thing that #linter documentation of errors raised seems to be coalescing around the "Problematic code / Correct code / Rationale" pattern.

Does anyone know if there's a name for this pattern of #documentation ?

The first tool I saw doing this was #shellcheck - here's an example of an error page: https://github.com/koalaman/shellcheck/wiki/SC2162

RuboCop : le flic du code qui ne plaisante pas avec les règles de style ! https://korben.info/rubocop-linter-ruby.html #Développement #robocop #rubocop #linter #ruby

I was surprised I couldn't find [*] a #precommit hook to run the #ChkTeX #LaTeX #linter via the pre-commit framework (https://pre-commit.com) for #git . It was trivial to create a new pre-commit configuration that simply runs chktex, I published a WIP repo under: https://github.com/meliache/pre-commit-chktex .
I contains two hooks: chktex-system, which uses the system executable and chktex-conda, which installs chktex via #conda. Still I think probably this already exists somewhere and I just missed it. 1/N

"to give you a sense of what he means with fast, common Python linters can take 30-60 seconds to lint the CPython codebase. Ruff takes 300 milliseconds."

https://talkpython.fm/episodes/show/400/ruff-the-fast-rust-based-python-linter

#python #rust #linter #podcast #devtools

If you use VS Code and write bash, but you're not actually very good at bash, ShellCheck is great. It'll show you where you make mistakes that can be non-obvious and encourage you to use modern syntax:
https://marketplace.visualstudio.com/items?itemName=timonwong.shellcheck
#vscode #bash #linter #shellcheck #code #shell

After ignoring #python #linter s for years about this "method may be static or a function" I decided to ask.

Whenever I write a Python class there are always some methods that do not use self. What is the actual recommendation for those?

Extract them as functions and have them in the same file as the class but out of the class hurt my #Java sensibility.

Having them as static methods seems cleaner but obscure at the same time...

Upgrading #angular - the code base has gotten very loosey goosey. I'm also implementing a #linter to try to teach the team how to tighten up the code base.

I'm learning a ton while doing it! Setting most of the rules to warnings. Again... To teach. Also... This is a 6 year old application with 1000's possibley10's of 1000's lines of code. Setting everything to error would be too overwhelming.

#webdev

#programming:
#Linter: '31 problems (0 errors, 31 warnings)'
#programmer: 'Everything is fine! Nothing to worry about!'