This should be safe for CSV and others.
We probably want to do a similar thing with messages (commands).
Remember: we should not log the raw data. (security issue)
The `name` property of a participant should probably be changed to `identifier`.
We might then add a (non necessarily unique) name for diplay only.
This is bad, since the regex will obliterate any non-latin character.
Need to check if `\P{Letter}` is supported in Godot.
I believe this commit closes the core feature loop.
Now, it's all about QoL improvements, bugfixes
and the dragon for which this project is meant to be a PoC:
DELEGATION
So far it's working quite well,
and it is rather pleasant to code.
There are no safeguards whatsoever for now.
They will come along with their tests :3
As detailed in previous commit with the unit-test (which now pass),
the regex is as follows :
(?<candidate>[a-zA-Z]{1})(?<grade>[0-9]{1})
We have room to support more than 25 candidates or 10 grades in the future.
Right now, this is enough, let's move on !
The data is a dummy, waiting to be connected to a provider like Twitch.
We also need to sort the profiles, and animate the sort ;)
The GUI elements will probably need more work as well (like clipping, etc.)
We also tried GUT in the past, so we wanted to try WAT this time.
We're not sure which would be easier to extend in order to add
a Gherkin parser and runner.