1244922 - JSON Viewer: improved search with syntax for filtering through data

Status: NEW

(DevTools :: JSON Viewer, defect, P3)

Description

[Bryan Clark (DevTools PM) [:clarkbw]]

Let's figure out a minimal syntax that makes sense to start with and I think we should reuse the filter help popup the debugger uses.

Also, keep in mind bug 1217131 which is about making the whole of found object accessible.

via bug 1223143 comment 7

> ## JSON tab - usability - filter box has limited value, can be frustrating
> 
> When exploring structured data, one will often have a lot of data with
> objects several levels deep and key/value pairs that look like e.g.:
> "relevant_info:4".
> 
> Searching for "relevant_info" will select all or most entries. Searching for
> "4" will yield a lot of false positives if the user intended to select all
> entries that had a value of "4" for "relevant_info".
> 
> There are situations where just searching keys and values for a string will
> be useful. But also many others where it will be unusable and frustrating.
> 
> Two ideas for data exploration:
> 
> 1. Filter by key:value pairs. Maybe with a special syntax in the filter
> field (like "relevant_info:=4", "relevant_info:<4", "relevant_info:text") or
> a dedicated, more discoverable UI.
> 
> 2. Filter (or maybe query, with a separated result view?) by path. For
> instance if we have data that looks like this:
> 
> [
> 	…,
> 	102: { x:"y", meta:{…}, … },
> 	…
> ]
> 
> We might use "[102]" to isolate "102: { x:"y", meta:{…}, … }".
> And we might use "[102][meta]" to isolate "meta:{…}".
> 
> Terminal featuritis, I know. :D

Comment 1

[Jan Honza Odvarko [:Honza] (always need-info? me)]

No activity here, moving to the backlog (P3)
Honza