kafbat/kafka-ui

FE: Messages: JSON path errors crash the page

Open

#1,436 opened on Oct 23, 2025

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)TypeScript (363 forks)auto 404
area/messagesgood first issuehacktoberfestscope/frontendstatus/triage/completedtype/bug

Repository metrics

Stars
 (2,554 stars)
PR merge metrics
 (PR metrics pending)

Description

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running main-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

if preview jsonPath expression causes some error, for example:

since previews are stored in the local storage of the browser. So if the preview does cause errors, the issue persists until it is removed.

And after clearing the kafbat-ui-message-preview value of the local storage, I was able to access the topic again.

Expected behavior

app should not save values causes error in local-storage, or try to delete it after error.

Your installation details

using kafbat 1.16.0 and helm chart

Steps to reproduce

use an invalid jsonPath expression in Preview

Screenshots

No response

Logs

No response

Additional context

No response

Contributor guide

Research direction
Investigate the message preview feature in the frontend code. Locate where JSONPath expressions are validated and how preview values are stored in localStorage under the key 'kafbat ui message preview'. Fix the code so that invalid JSONPath expressions are not saved to localStorage, or ensure they are removed when an error occurs.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75