-
Notifications
You must be signed in to change notification settings - Fork 890
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
Easily view nested structured data in Discover #5459
Comments
There is also a PR to enhance the fields that are available on the left-menu: #5429. |
If neither of those options are what you were looking for, please add some details of your vision and reopen this issue. |
@AMoo-Miki I have clarified the description of this issue. I am aware of the existing JSON view present in new Discover, I believe this is insufficient for the kind of quick structural comparison it needs to support. My request is to display specific JSON in each row to quickly compare dozens of rows without having to click open the full JSON view. Please let me know if my description is not clear enough. Could you please re-open this issue? it appears I lack the permissions. |
Let's say I have a nested object that I want to compare between records. If a record has a lot of data, the values you might not be able to see a field in the in-line list view, meaning you have to use the 'Inspect document details' pop-out view (as highlighted in Amoo-Miki's comment below). This sidebar view only allows you to see the structure of one document/row at a time, which makes quickly comparing values between rows very painful.
I propose having a column option that lets you toggle a column to display a full multi-line pretty JSON version of a field. This would let you quickly compare each record's value for a nested object without needing to click each row to open an alternative view.
Here's a rough mock-up
I believe this is a critical feature for exploring the possible fields of dynamic records. Since you don't know what specific fields exist, being able to drill down in a structured way helps find seldom-used fields and build understanding of how fields relate to one another.
Additional Suggestions
Another benefit of the JSON view is making it easy to display arrays of objects. If you have
object.array.obj.obj.value
, and a column forobject.obj.obj.value
, the column could simply map theobject.array
accordingly and display the result as a JSON array .for instance consider a document containing the following data:
A JSON column in the document display showing the value
items.create.error
could display the following:The text was updated successfully, but these errors were encountered: