Skip to content

feat: requirement of search in available fields #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
WINOFFRG opened this issue Feb 17, 2025 · 3 comments
Open

feat: requirement of search in available fields #25

WINOFFRG opened this issue Feb 17, 2025 · 3 comments

Comments

@WINOFFRG
Copy link

Hi,

We are looking for a search for fields present in the data. In case of large number of fields if becomes difficult to always scroll down.

Image
@mxkaske
Copy link
Member

mxkaske commented Feb 20, 2025

I am not sure if I totally understood. What is the type of your field?

If it's a checkbox, we render an input when more than 4 options are available.

If that's an input, we leave it blank. It would be great to replace it with a combox or also support checkboxes with the available options to show the user what the options are (similar to what vercel is doing).

@WINOFFRG
Copy link
Author

Okay understood, Clarifying this. See in case you have several top level fields, consider you are logging objects with large number of keys. Usually during debugging we play with those fields like filtering them or changing their state so we just use search for it. You can refer the "Search fields.." input above, just typing in the field we select it right away. In current scenario we would have to scroll through a large list of fields.

@mxkaske
Copy link
Member

mxkaske commented Feb 24, 2025

How about having a Combobox instead to suggest best matching values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants