kafbat/kafka-ui

Replace `1.0-UNKNOWN` version string with less ambiguous `UNKNOWN`

Open

#831 opened on Feb 7, 2025

View on GitHubContributor guide
 (6 comments) (0 reactions) (0 assignees)TypeScript (363 forks)auto 404
good first issuescope/backendstatus/triage/completedtype/chore

Repository metrics

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

Description

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

https://github.com/kafbat/kafka-ui/blob/main/api/src/main/java/io/kafbat/ui/service/ReactiveAdminClient.java#L154

String version = "1.0-UNKNOWN";

The 1.0-UNKNOWN looks a bit ambiguous and confusing and people tend to be asking version of what it is: Image Image

Can this be changed to just UNKNOWN please? (not sure why Kafka-UI can't identify version of AWS MSK 🤷🏻)

Describe the feature you're interested in

Reduce ambiguity of unidentified cluster(?) version string.

Describe alternatives you've considered

No response

Version you're running

v1.1.0

Additional context

Let me know and I'll create a PR if this change isn't going to break something else (I'm a way not familiar with Java). Thank you.

Contributor guide

Research direction
Inspect the version string in ReactiveAdminClient.java and check for any logic that relies on the '1.0 UNKNOWN' format. Search for usages of this variable to ensure changing it to 'UNKNOWN' will not break anything.
Tech stack
java
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85