Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.30%. Comparing base (9ef5803) to head (877061f).

@@           Coverage Diff            @@
##           develop     #815   +/-   ##
========================================
  Coverage    97.30%   97.30%           
========================================
  Files           83       83           
  Lines        10798    10798           
========================================
  Hits         10507    10507           
  Misses         291      291           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I think it's a great tool that contributors can spin locally and submit their results to the project.
But making project infrastructure slim has become a security priority.
Tracking decencies tree I wonder, does it worth it? I tried it locally and saw the poetry.lock file grows significantly, so I think we don't need to mandate its use.

pymarkdownlnt 0.9.34 A GitHub Flavored Markdown compliant Markdown linter.
├── application-properties >=0.9.0
│   ├── pyjson5 >=1.6.9 
│   ├── pyyaml >=5.4.1 
│   ├── tomli >=2.0.1 
│   └── typing-extensions >=4.5.0 
├── columnar >=1.4.0
│   ├── toolz * 
│   └── wcwidth * 
└── typing-extensions >=4.5.0

We can add only on CI then, or close

I would repurpose the PR to lint files, the single one it targets now, or more, without adding weight to the project with tools and enforcements. It would be very welcome.

I would repurpose the PR to lint files, the single one it targets now, or more, without adding weight to the project with tools and enforcements. It would be very welcome.

Done

This PR still don't have lint changes to files. We can't designate Github actions without knowing the impact on CI, code and docs. First the changes must be done locally, then we can evaluate the tools that made it.