Problem description (Describe the problem you would like to solve with this feature request or suggested idea).
Redis Strings are binary-safe, and many applications store encoded or binary data in Redis. When viewing these values in Redis Insight, they are often displayed as unreadable raw data, making them difficult to inspect and debug.
I opened a PR feat(ui): Add value decoder directly because I'm already heavily using this functionality in my own system for debugging.
If you don't think this feature is necessary, if it isn't aligned with the project's roadmap, or if it requires further changes, please let me know and I'll be happy to update or close the PR๐.
How often do you encounter this problem (Describe how frequently this problem occurs).
Very frequently.
This is a common workflow in my own system, where binary data is stored in Redis for performance reasons. Similar use cases are also common in games and other high-performance systems.
Alternatives considered (Describe any alternative features or products you've considered).
The main alternative is manually decoding values outside Redis Insight, for example by writing custom scripts or using separate debugging tools. However, this is inconvenient and significantly slows down debugging.
Additional information (Add any other context or details here).
The proposed design is extensible. While the initial implementation only includes a Binary Decoder, the framework could later support additional formats such as Protobuf, MessagePack, BSON, or other custom decoders.
Problem description (Describe the problem you would like to solve with this feature request or suggested idea).
Redis Strings are binary-safe, and many applications store encoded or binary data in Redis. When viewing these values in Redis Insight, they are often displayed as unreadable raw data, making them difficult to inspect and debug.
I opened a PR feat(ui): Add value decoder directly because I'm already heavily using this functionality in my own system for debugging.
If you don't think this feature is necessary, if it isn't aligned with the project's roadmap, or if it requires further changes, please let me know and I'll be happy to update or close the PR๐.
How often do you encounter this problem (Describe how frequently this problem occurs).
Very frequently.
This is a common workflow in my own system, where binary data is stored in Redis for performance reasons. Similar use cases are also common in games and other high-performance systems.
Alternatives considered (Describe any alternative features or products you've considered).
The main alternative is manually decoding values outside Redis Insight, for example by writing custom scripts or using separate debugging tools. However, this is inconvenient and significantly slows down debugging.
Additional information (Add any other context or details here).
The proposed design is extensible. While the initial implementation only includes a Binary Decoder, the framework could later support additional formats such as Protobuf, MessagePack, BSON, or other custom decoders.