It also looks like your eslint config broke the CI, could you look at that ? No idea what caused it

It also looks like your eslint config broke the CI, could you look at that ? No idea what caused it

On main currently if npm run lint is executed there seems to be an error in useLanguages.tsx. Maybe these were merged around the same time before this file could be correctly linted?

I fixed it, was due to the node version being 16 and eslint v9 supporting only node v18+

It also looks like your eslint config broke the CI, could you look at that ? No idea what caused it

@Mathys-Gasnier I think it may actually be that we're using an older version of node:
Screenshot 2025年01月01日 at 21 00 00

Switching to node v16.20.2 causes the same error on local:
Screenshot 2025年01月01日 at 21 02 29

I fixed it, was due to the node version being 16 and eslint v9 supporting only node v18+

You found the same issue as me, thanks 😄

Would you be able to add a CI or edit an existing one to run all linting, cspell, and all of that ?

Appart from that it looks wonderfull

Let me take a look at this.

@Mathys-Gasnier Just merged the latest changes; should the following be "contents" and not "content"?

check-snippets.yml
Screenshot 2025年01月01日 at 21 08 37

It should yeah, i'm going to push a commit fixing the typo

@Mathys-Gasnier I've added a new workflow "pre-commit-checks.yml" which seems to be working correctly. Currently it will execute on push and pull_request for any branch or PR, but feel free to changes this if it is not restrictive enough.

I think you can keep it just on pull requests, we only really need to check this when merging a PR

This has been changed.

Looks magnificent, let's wait on another review and we can then merge this

As you fixed what @psychlone77 said, I think we are safe to merge this, great work !