Make the logs have unique id for each message in front of each log line #294

New Issue

MrUnknownDE · 2026-04-05T17:52:27+02:00

MrUnknownDE commented

2026-04-05 17:52:27 +02:00

Originally created by @loucass003 on 1/31/2023

In the gui or the server there is instances where we look for some specific lines of logs in the serial to do other actions.
it can causes issues if someone decides to change de text of that log line to something else and forget to change the server or gui that are lookig for it.

My proposal is that each log lines have their unique id. kinda like error id but for everything. Log lines that hold data would be the execption because you have to actually parse the log line to get data. but for all the others like

looking for server...
handshake successfull

it would be better to have something like

{1} looking for server ....
{34} handshake successfull ...

that way code inside the server could just use the id as a reference instead of the log text

*Originally created by @loucass003 on 1/31/2023* In the gui or the server there is instances where we look for some specific lines of logs in the serial to do other actions. it can causes issues if someone decides to change de text of that log line to something else and forget to change the server or gui that are lookig for it. My proposal is that each log lines have their unique id. kinda like error id but for everything. Log lines that hold data would be the execption because you have to actually parse the log line to get data. but for all the others like ``looking for server...`` ``handshake successfull`` it would be better to have something like `` {1} looking for server ....`` `` {34} handshake successfull ...`` that way code inside the server could just use the id as a reference instead of the log text

MrUnknownDE added the Type: Enhancement Type: Discussion Priority: Normal Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Enhancement Type: Discussion Type: Discussion Type: Discussion Priority: Normal Priority: Normal Priority: Normal Priority: Normal Priority: Normal labels 2026-04-05 17:52:29 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/SlimeVR-Tracker-ESP#294