We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently it is quite hard to debug waku issues (context), as we're not logging message IDs.
To simplify this, I propose adding the same option that the desktop version provides when “DEBUG” mode is enabled:
This would allow QAs and developers to locate faulty messages more easily by providing a unique identifier for each message.
The option "Copy Message ID" can be implemented using the existing API_LOGGING_ENABLED flag (of course can be done separately, this is a suggestion)
The text was updated successfully, but these errors were encountered:
cc @ilmotta may be we can squeeze it to 2.34?
Sorry, something went wrong.
I think it's doable to squeeze this in 2.33 because it's a quick win. Let me grab this one @churik
ilmotta
No branches or pull requests
Problem
Currently it is quite hard to debug waku issues (context), as we're not logging message IDs.
To simplify this, I propose adding the same option that the desktop version provides when “DEBUG” mode is enabled:
This would allow QAs and developers to locate faulty messages more easily by providing a unique identifier for each message.
Acceptance criteria
The option "Copy Message ID" can be implemented using the existing API_LOGGING_ENABLED flag (of course can be done separately, this is a suggestion)
The text was updated successfully, but these errors were encountered: