redpanda-data / redpanda-data/console
Consider "toning down" the error UI when unable to deserialise values
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
At the moment, we report this as Errors were encountered when deserializing this message, which is true, but also doesn't account for the case where the data is actually just raw bytes and so this is expected. We also then show the actual bytes almost as a footer to the list of errors, so it's easy to overlook them.
Perhaps we could emphasise the raw bytes in these cases, and then list that we were unable to match them to any common encoding below?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Locate the UI entry point that renders deserialization errors and raw bytes, then inspect how encoding failures are presented. Done means raw bytes are prominent when appropriate and the fallback explanation clearly states that no common encoding matched, with coverage for the affected display behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100