Consistent casing for classes and ids

[sarahsporck]

Motivation

See discussion in #2534

We're not 100% consistent in our code base, but I think kebab-case is more common in our id and class attributes than snake_case.
We could decide on consistent case conventions and then document them to facilitate such decisions in the future...

I think at the moment, these are the most used variants:

Python code: snake_case
Python file names: snake_case
TypeScript code: camelCase
TypeScript file names: kebab-case
HTML code: kebab-case
HTML file names: snake_case

The question is whether we should keep this as standard, or whether we should adapt one or more of these categories...

Proposed Solution

Decide for consistent solution regarding casing.
Then check wether all files, ... follow this decisicon and fix it up if necessary. There might be linting rules for this (for eslint and pylint, at least).

The linting should be solved in #3779

Alternatives

Don't change anything. It's not worth the effort.

User Story

As a developer I want consistently use class properties and ids so that I can efficiently deliver more features.

[abastola0]

Hi. can you please assign me this issue?

[timobrembeck]

Hi @abastola0 thanks a lot for your interest in our project, unfortunately we still need to finalize this task before somebody can start working on it.
If you'd like, you can have a look at our other good first issues and see if you're interested in something else in the meantime (and feel free to ask for details about a specific task if its description is too brief).

[abastola0]

Sure @timobrembeck. Please let me know if it's up for contribution.

[MizukiTemma]

From Issue Grooming on 07.07.2025

Potential difficulty: as we pass between TS (CamelCase) and Python (snake_case) id numbers etc, it may be difficult to stay consistent with casing.

Idea: Force linters to check casing -> A separate issue.