redpanda-data / redpanda-data/console

Search text field replaces input with scientific notation number

Open Beginner friendly
#2,459 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4.3k
Forks
432
Avg merge
3d 6h
Merged PRs (30d)
40

Description

I was trying to search for a partial uuid in the consumer groups and topics using redpanda console, and then i found that my input got magically converted into scientific number notation. It took me a while to realize it did that, and i was real confused why I couldn't find my topic. 😄

Steps to reproduce:

  1. Go to topics or consumer groups page
  2. Either paste or type in a string in the search field which has the format <numbers>e<numbers>, such as 1461e229

Observed behavior:
The text gets replaced with scientific number notation. For example: 1461e229 gets converted into 1.461e+232.

Expected behavior:
That my text is not replaced with scientific number notation, so it actually searches for what I typed in.

Note
If you search by typing in "1461e229" (with the quotation marks), then you can search for the literal string.
I'm not sure if it's intended behavior, but at least it can be made more clear that the value is automatically replaced.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the search fields used on the topics and consumer groups pages, then reproduce the issue with 1461e229. Trace where the input is parsed or formatted; done means strings matching this pattern remain unchanged and can be searched literally.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend, search
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.