GeezerVison

@silversonicaxel would you be able to rebase your branch such that the linting changes are all in one commit? It makes it hard to review when they're all mixed in.

@camdecoster

I undid most of them, (sorry I had global linter in the IDE)

But the last left, seem legit to me.

And project linting was not complaining, or fixing it in its execution.

    "lint": "npx @biomejs/biome lint",
    "lint-fix": "npx @biomejs/biome format ./test/image/mocks --write; npx @biomejs/biome lint --write || true",

I'm totally fine with linting. It just helps to move all those changes into one commit, then make the actual PR changes in separate commits. I'll take a look at things right now, but you could make a final commit to lint after the review is complete.

FYI, the test failures are unrelated to your changes.

Working for me. You can add back your linting changes if you'd like.

I would prefer another PR, where lint rules are applied stricter. Otherwise I would feel to push my IDE lint rules to just a few bunch of files.