webhint helps you improve your site's accessibility, speed, cross-browser compatibility, and more by checking your code for best practices and common errors.
Available as:
- VS Code extension
- browser extension
- CLI program
... and how to use them in CI pipelines.
Comparing W3C v.Nu HTML checke, html-tidy, htmlhint, html-validate, LintHTML and html-eslint.

This last option makes it easy to setup a HTML linter in Gitlab CI pipelines:
lint-html:
stage: test
script:
- apt update -y && apt install -y curl unzip
- ... # generate HTML content in public/
- curl -ROLs https://github.com/validator/validator/releases/download/latest/vnu.linux.zip
- unzip vnu.linux.zip
- vnu-runtime-image/bin/vnu --skip-non-html public/
A very short blog post to share some minimal code snippets on how to quickly and easily setup Gitlab CI pipelines to run static code analysis tools on C++ code and Jenkins pipelines (or any Groovy code).
Pylint is a great static code analyser for Python code. I have been using it for several years, in various projects, and it's simple to use yet very powerful.
I even contributed to Pylint by submitting a new rule a few years ago : implicit-str-concat.
For an introduction to Pylint, you …
CLI to analyze IaC: Terraform, CloudFormation, Kubernetes, Helm, ARM Templates and Serverless framework
Today, I am happy to announce a new version 2.2.0 of fpdf2 !
https://github.com/alexanderankin/pyfpdf/
Doc: https://alexanderankin.github.io/pyfpdf/
During the last few months, I contributed a few improvements to fpdf2
,
David Ankin fork of PyFPDF
,
the user-friendly Python library to generate PDFs:
from …
Quelques éléments pour démarrer avec Gitlab CI
Script to install Datalogics PDF Checker CLI on a Linux system:
curl https://raw.githubusercontent.com/Lucas-C/dotfiles_and_notes/master/bin/install-pdfchecker.sh | bash
PDF_Checker/pdfchecker --profile PDF_Checker/CheckerProfiles/everything.json --input $pdf
I have compiled a list of tools you might find helpful for testing structured data markup and rich snippet display (microdata, RDFa, RDFa Lite and JSON-LD)
bash -n
is a basic but useful builtin syntax linter.
If you do not use the pre-commit
Python command & hook manager (check it out, it's great!), you can define a git
pre-commit hook "manually" by putting the following in a file at .git/hooks/pre-commit
:
#!/bin/sh
# Redirect output to stderr:
exec 1>&2
echo "Executing bash native syntax linter on all modified .sh files:"
if ! git diff --cached --name-only --diff-filter=AM HEAD | grep '.sh$' | xargs -n 1 bash -n
then
echo "Error : syntax issues were detected"
exit 1
fi
- What it was / was'nt designed to do?
The key takeaway should be that type hints are designed to improve developer experience, not to influence how your script evaluates. It creates happy developers, not faster code!
- What kind of type system?
- Gotchas
- Tools
eslint rules from airnbnb to validate ReactJS code