Code
The Tablo ecosystem is written in C++ 20.
Variables
Variables are named using Camel Case. Choose variable names that are intuitively understandable.
It is better to opt for an explicit, longer variable name than for one that only becomes clear through the context of the code.
For class-level variables, use the this-> keyword (e.g., this->myVariableName).
Files
Files are named using Snake Case.
This makes the filenames easier to read and helps distinguish them from variable names (e.g., my_new_file.cpp).
Folders
Try to name folders using a single word. If that is not possible, use Camel Case for the folder names.
When several files clearly belong together, group them into a single folder to ensure the structure is intuitively understandable. (e.g., folder, myFolder)
Commits
A commit should contain only what is described in the commit message. If you are committing code that relates to an issue,
please link to it using its number (e.g., #9).
If multiple commits are required to solve the problem, you can create a branch and link the issue to that branch. Please solve only one single issue per pull request,
unless you are a direct member of the Tablo projects. In addition add a prefix to your commit message (e.g., update: your commit).