You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm always frustrated when I need to categorize or label log messages in my app. Without a built-in way to add a name or tag, it becomes difficult to distinguish logs coming from different parts of the app, especially when debugging large applications.
Describe the solution you'd like
I would like to have a name or tag parameter for log messages. This would allow me to easily categorize or label logs when using the flutter_talker package. For example:
talker.debug('Test message', name:'MyCustomTag');
This would output:
[MyCustomTag]Testmessage
Allowing for consistent categorization across all log levels (debug, info, warn, error).
Describe alternatives you've considered
As an alternative, I could manually add the name or tag in the log message, but this becomes cumbersome and doesn't provide the same level of integration or convenience that a dedicated name parameter would offer.
Additional context
Currently, the default tag used for all logs is 'Talker', which can be found in the code at
Hello @weitsai 👋
This custom tag [MyCustomTag] available only on apple devices (iOS, MacOS)
On Android, Windows, Linux and other operating systems logs looks like default flutter messages (with custom colors)
I think that we will not add a feature that will be available on only 2 of the supported Flutter platforms.
Hello @weitsai 👋 This custom tag [MyCustomTag] available only on apple devices (iOS, MacOS) On Android, Windows, Linux and other operating systems logs looks like default flutter messages (with custom colors)
I think that we will not add a feature that will be available on only 2 of the supported Flutter platforms.
I’d like to suggest reconsidering the name or custom tag feature for logs. Even if it’s primarily useful during development, being able to filter logs by [MyCustomTag] in Flutter's Debug Console (e.g., in VS Code or Android Studio) would significantly improve debugging for larger apps.
I'm always frustrated when I need to categorize or label log messages in my app. Without a built-in way to add a name or tag, it becomes difficult to distinguish logs coming from different parts of the app, especially when debugging large applications.
Describe the solution you'd like
I would like to have a name or tag parameter for log messages. This would allow me to easily categorize or label logs when using the flutter_talker package. For example:
This would output:
Allowing for consistent categorization across all log levels (debug, info, warn, error).
Describe alternatives you've considered
As an alternative, I could manually add the name or tag in the log message, but this becomes cumbersome and doesn't provide the same level of integration or convenience that a dedicated name parameter would offer.
Additional context
Currently, the default tag used for all logs is 'Talker', which can be found in the code at
talker/packages/talker_flutter/lib/src/extensions/talker_flutter.dart
Line 30 in 8eff2a8
Adding the ability to specify a custom tag would allow for better log management, especially in larger applications.
The text was updated successfully, but these errors were encountered: