Skip to content
New issue

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

Add color customization for TalkerLog in TalkerScreen #252

Open
Rodsevich opened this issue Jul 30, 2024 · 1 comment · May be fixed by #272
Open

Add color customization for TalkerLog in TalkerScreen #252

Rodsevich opened this issue Jul 30, 2024 · 1 comment · May be fixed by #272
Labels
enhancement New feature or request open-to-contribution You can open Pull-request to resolve this issue

Comments

@Rodsevich
Copy link

Is your feature request related to a problem? Please describe.
If you create a custom log (suppose a metric/setting/etc) you must attain to the default grey color because of limitations on the enums Talker uses.

Describe the solution you'd like
I'd love you can define another property in the TalkerLog for enforcing the color for those logs.

Describe alternatives you've considered
I have no way of tweaking the behavior as a user, the only alternative was to forfeit the color I need.

Additional context
Enums can't be extended, but sealed classes can. Taking in consideration that enums will never be extended and custom logs are a thing needed, why can't we change to classes approach instead of enums?

@Mooyeee
Copy link

Mooyeee commented Jul 31, 2024

This was actually something I was thinking about too, I may play around a bit when I get some time since it would be very useful.

@Frezyx Frezyx added enhancement New feature or request open-to-contribution You can open Pull-request to resolve this issue labels Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request open-to-contribution You can open Pull-request to resolve this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants