kafbat/kafka-ui

FE: KC: Pasting a config doesn't trigger form validation

Open

#514 opened on Jul 31, 2024

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)TypeScript (363 forks)auto 404
area/connectarea/uxgood first issuescope/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)

Copy paste a changed config into the Connectors Form. Now the Submit button is still disabled despite a valid and different JSON is in the Form.

Expected behavior

The Input validation should happen when a JSON config is copy pasted into the Form

Your installation details

Docker, with 8c7012679d7ec0293e0f96a1740690bf0bfc994e

Steps to reproduce

Copy the existing config into an external editor, place that password back in, edit some JSON fields and then copy paste into the Form.

Screenshots

No response

Logs

No response

Additional context

No response

Contributor guide

Research direction
Reproduce the bug by pasting a modified config into the Connectors form. Find the component responsible for the form and inspect how the config field updates on paste. Trace the validation logic to see why it does not trigger on paste, and add a handler to validate on paste or use an existing change detection mechanism.
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65